The decline might be because instance owners have strengthened the account creation process. I remember in “the early days” how there were an insane amount of bots, but now it seems like most of them have been banned or mitigated.
Sorry for scaring developers
Norwegian proot with a taste for shitposting Deeply sorry for my photoshop creation
Former account at Kbin
aspe:keyoxide.org:JYRRSWIKLZWX366Y4DONCIEYAE
The decline might be because instance owners have strengthened the account creation process. I remember in “the early days” how there were an insane amount of bots, but now it seems like most of them have been banned or mitigated.
Maybe building one yourself might be a good idea. I found someone’s old desktop with an 8th Gen i7, 32gb of ram, mobo and Gtx 1070 gpu on the side of the road while on a road trip. Thing was sitting in the rain and slightly rusted, but when I cleaned off the corrosion, stuffed it full of hdds and set it up with truenas scale it’s been running flawlessly with an uptime of almost a year. Been running like that for about 5 years now with the occasional maintenance.
If you’re the owner of the website, I suggest you look into those php errors
Warning: simplexml_load_file(https://feeds.thefossrant.com/rss_feed.xml): failed to open stream: php_network_getaddresses: getaddrinfo failed: No address associated with hostname in /var/www/html/article.php on line 2
Warning: simplexml_load_file(): I/O warning : failed to load external entity "https://feeds.thefossrant.com/rss_feed.xml" in /var/www/html/article.php on line 2
Warning: Invalid argument supplied for foreach() in /var/www/html/article.php on line 5
Warning: Invalid argument supplied for foreach() in /var/www/html/article.php on line 19
Published on: 1970-01-01 00:00:00 UTC
Tags:
Image unavailable
I switched from duckdns about a year ago as it failed to resolve the addresses for my jellyfin server. I ended up buying a domain from cloudflare for 3 years for about $4, and I self-hosted ddns updater to automatically grab the dynamic ip, and set it to a subdomain.
As for your nginx config, I’d imagine you could make 2 separate config files in
sites-enabled
that are nearly identical, but listen for different domains. Something like this:#config file 1 server { listen 80; server_name example_a.com; location / { return 301 http://example_c.com$request_uri; #or use an ip instead of example_c.com } } #config file 2 server { listen 80; server_name example_b.com; location / { return 301 http://example_c.com$request_uri; #or use an ip instead of example_c.com } } #Or use "proxy_pass http://example_c.com;" in the location tag instead of "return 301..." if you want to reverse proxy the traffic