Welp, that was an adventure x_x
Trying to solve the issue throughout the afternoon of custom emojis being broken (like a GOP Congressman's marriage) due to permissions issues (which wasn't budging at all even after trying out bajillions of commands), I learned from a fellow Fedizen that nginx being outdated on my server was contributing to the issue. However, when updating to nginx's newest version, shit hit the fan for both the instance and my personal webspace. Both of them just wouldn't connect on the web browser, no matter if I reloaded the page, cleared cache, restarted Cherrypick's Docker containers, or even rebooted the entire server. Yet, literally everything looked fine. Reading Digital Ocean's page on troubleshooting common nginx errors, all the commands returned successes. The systemctl command reported that nginx was active, the firewall is allowing traffic from Nginx, the error log reported nothing broken, and the configuration file had no syntax errors. Even the ping command displayed no packet loss. However, after chatting with another Fedizen, they pointed out how one line, "include /etc/nginx/sites-enabled/" was missing from nginx.conf. So, when I then edited the file to include that line, after restarting nginx for the final time, shit just worked again. Even the emojis are normal. It was like the problem was wished away. Still, this was a hell of a lot. I think it took multiple hours for me to deal with all this troubleshooting, not to mention how stressful everything breaking apart obviously is.
At least the server has been de-shittified :S
(Btw, thank you two (you know who you are ^w^) for helping me out with this mess. System administration in general requires a lot of help from others, whether they are forums, articles, documentation. That's ironically one of the most human things in general, especially in the otherwise cold (and frankly, chud-infested) tech space.)
This website by Poppy Farbird is licensed under CC BY-SA 4.0