My hosting setup just got more complex

So as many of you know I develop a Linux distro called Drauger OS.

A few days ago, someone hacked into the server hosting the apt repository and messed with one of the websites the repository was sharing the server with. The repository wasn’t tampered with, but the server is now effectively unusable without a complete reinstall process.

Because of all this, I ended up moving to my personal server.

My initial idea was to have nginx be a reverse proxy for the apt repository, another subdomain for downloading files, and my NextCloud. All of which would use Apache for their web server. That ended up not happening. NextCloud was refusing to move ports (a phenomenon I eventually rectified with a couple snap set nextcloud commands) so my NextCloud installations have basically got to reinitialize themselves with the server.

Something wasn’t working with the previous idea of settting up Apache and serving it over the reverse proxy with Nginx. I ended up just serving both the apt repo and download folder using nginx. I still would like to get the reverse proxy set up for NextCloud but that’s not looking feasible.

Moral of the story: make sure no one can hack the server you are on. Whether it be through your site or someone else’s.

1 Like

Perhaps you could use’s Docker container for Nextcloud instead of the Snap. Getting set up with docker-compse is quite easy, and it is a simple matter to map any given port inside the container to a different port outside the container. Instead of having to muck about with Nextcloud’s settings, you can simply set the external port to whatever you want and trick Nextcloud into thinking it is using the default! :wink:

Once I figured out what I was doing it was fine. I also talked a friend into SSHing into and getting Nginx set up to reverse proxy two of the websites on the server while Nextcloud user Apache and Pihole used Lighttpd

Alright. Glad things worked out for you.