😆 That moment when you thwart a ddos-like sftp attack that's been going on for DAYS with over a MILLION hits just by changing the sftp port 🤣 #cybersecurity #security #serveradmin #wazuh #security #it #tech #funny
#cybersecurity #security #serveradmin #wazuh #IT #Tech #funny
I’ve written up my findings in what appeared to be the most relevant issue on GitHub.
https://github.com/mastodon/mastodon/issues/5774#issuecomment-1663144706
Nope, I’ve swapped it back.
Very interesting. Using WEB_DOMAIN=social.dvsn.net and ALTERNATE_DOMAINS=dvsn.net resulted in posts no longer appearing on my test account on a different server. I’ll bet followers didn’t get to see the nice sunflower.
I guess that’s the nature of federation with Mastodon. If there’s no point at which the software checks for domain alterations then there’s no way I can influence a remote server to change its behaviour. It’s a done deal.
I’ll leave it like this for now with both configured, in the hope other servers will eventually “learn” to use the subdomain. But in all likelihood this won’t happen and I’ll be left with both, maybe with pre-change servers always using dvsn.net and post-change servers using social.dvsn.net.
Ah, well. It’s all part of the fun.
I’ll leave it like this for now with both configured, in the hope other servers will eventually “learn” to use the subdomain. But in all likelihood this won’t happen and I’ll be left with both, maybe with pre-change servers always using dvsn.net and post-change servers using social.dvsn.net.
Ah, well. It’s all part of the fun.
Got curious and swapped to WEB_DOMAIN=social.dvsn.net and ALTERNATE_DOMAINS=dvsn.net.
Seems to still be working.
What happened before was everything being fine, except my incoming feed from other servers was dead. I could use my own system without issue, but clearly other servers were expecting to contact this server on dvsn.net and not even the webfinger redirect to social.dvsn.net would change their mind.
Got curious and swapped to WEB_DOMAIN=social.dvsn.net and ALTERNATE_DOMAINS=dvsn.net.
Seems to still be working.
What happened before was everything being fine, except my incoming feed from other servers was dead. I could use my own system without issue, but clearly other servers were expecting to contact this server on dvsn.net and not even the webfinger redirect to social.dvsn.net would change their mind.
What I’ve done instead is leave the subdomain up and running, configured using ALTERNATE_DOMAINS=social.dvsn.net, and I can use Mastodon on either the bare domain or the subdomain now.
At some point in the future I’ll try swapping the subdomain into WEB_DOMAIN and putting the bare domain under ALTERNATE_DOMAINS. Which will probably break everything and cause a fire.
I’m going to log in via the subdomain from now on and see if there’s any change in the traffic over time.
What I’ve done instead is leave social.dvsn.net up and running, configured using ALTERNATE_DOMAINS=social.dvsn.net, and I can sign in and use Mastodon on either the bare domain or the subdomain now. At some point in the future I’ll try making the subdomain the WEB_DOMAIN and putting the bare domain under ALTERNATE_DOMAINS. Which will probably break everything and cause a fire.
The idea was to leave LOCAL_DOMAIN=dvsn.net, set WEB_DOMAIN=social.dvsn.net and then proxy the webfinger requests (as demonstrated in the docs linked above). That was all configured correctly, but remote servers would not visit the subdomain, I guess due to the time already federated and other server’s understanding of this server.
The idea was to leave LOCAL_DOMAIN=dvsn.net, set WEB_DOMAIN=social.dvsn.net and then proxy the webfinger requests (as demonstrated in the docs linked above). That was all configured correctly, but remote servers would not visit the subdomain, I guess due to the time already federated and other server’s understanding of this server.
Tried an experiment of running this server from social.dvsn.net instead of dvsn.net with redirects yesterday and it didn’t go well. I misunderstood that both the LOCAL_DOMAIN and WEB_DOMAIN need to stay the same once your server has started federating. As the docs say:
https://docs.joinmastodon.org/admin/config/#web_domain
> …the issues lie with remote servers’ understanding of your accounts, re-installing Mastodon from scratch will not fix the issue.
Oops. It did indeed break.
The only part that's still a work-in-progress is the #Grafana alerting configuration- does anyone have any recommendations for some general alerting templates/configs? #ServerAdmin #SysAdmin
#grafana #serveradmin #sysadmin
Question for #sysadmin #serveradmin #hpc #linux
Does a very busy /tmp slowdown the nfs storage?
Currently I am testing to change the TMPDIR env variable to minimize the impact on the /tmp directory.
In my experience several applications can be slowdown if the /tmp is very full, but I don't now about nfs.
#sysadmin #serveradmin #hpc #linux
Cloudflare Tunnel で自宅サーバー公開|荒川仁志
https://note.com/hitoshiarakawa/n/n482966cdacdc
#server #serveradmin
Debian 11 Bullseye : KVM : 仮想マシンを作成する : Server World
https://www.server-world.info/query?os=Debian_11&p=kvm&f=2
#server #serveradmin
Let's EncryptのSSL証明書の新しいサーバーへの引っ越し作業 - Ubuntuサーバー構築入門 - Ubuntuサーバーでゼロから環境構築
https://ubuntu.perlzemi.com/blog/20200619081050.html
#server #serveradmin
Upgraded to Mastodon v4.1.3 - looks like running smooth. As usual, updating my guide detailing whole process and problem solutions (including Node and Ruby upgrades, etc.): https://inretio.org/threads/update-mastodon-server-instance.11/ #serveradmin #fediadmin