Root servers

Reverse proxy with Nginx: several services on one root server

Website, Nextcloud and bots under their own subdomains with their own certificate: Nginx as the central entrance, step by step.

6 min readUpdated 17.11.2026FameSystems editorial team
In short

A reverse proxy is the one service that listens on ports 80 and 443 to the outside and passes requests to the right application based on the hostname. This way a website, Nextcloud, a Node.js service and a game server panel run on one root server under their own subdomains, each with its own certificate. With Nginx that is one configuration file per service.

The principle

Every application only listens locally on its own port, such as 127.0.0.1:3000. Nginx accepts all requests from outside, checks the hostname and forwards them to the matching port. Advantages: one central place for certificates, access rules and logs, and no service has to speak HTTPS itself.

Installing Nginx and creating a service

  • apt install nginx, then open ports 80 and 443 in ufw.
  • One file per service in /etc/nginx/sites-available/, e.g. app.your-domain.de.
  • In it a server block with server_name app.your-domain.de and location / { proxy_pass http://127.0.0.1:3000; }
  • Forward the headers Host, X-Real-IP and X-Forwarded-Proto, otherwise the application only sees the proxy.
  • Symlink to sites-enabled, nginx -t to test, systemctl reload nginx.

HTTPS with Let's Encrypt

Certbot obtains free certificates and renews them automatically: apt install certbot python3-certbot-nginx, then certbot --nginx -d app.your-domain.de. Certbot enters the certificate paths in the server block and sets up the redirect from HTTP to HTTPS. Requirement: the subdomain points to the server via a DNS A record.

WebSockets, uploads and timeouts

ApplicationSettingWhy
Chat, panels, live dataproxy_set_header Upgrade and Connection "upgrade"WebSockets need the connection upgrade
Nextcloud, uploadsclient_max_body_size 2GDefault is 1 MB
Long computationsproxy_read_timeout 300Default timeout is 60 seconds
Docker containersPublish ports on 127.0.0.1 onlyOtherwise the container bypasses proxy and firewall

Security at the proxy

  • Restrict admin interfaces to your IP via allow/deny or protect them with basic auth.
  • Rate limiting with limit_req against brute force on login pages.
  • Hide the server version: server_tokens off.
  • Keep access logs, Fail2ban reads them.
At FameSystems, Arbor mitigation intercepts network-level DDoS attacks in front of the server. The proxy protects the application layer: logins, uploads, malformed requests.
Matching product

Root server for several services

Dedicated cores and RAM, NVMe, your own kernel control. Ideal for proxy, website, Nextcloud and bots on one machine.

Published 17.11.2026Updated 17.11.2026

Frequently asked questions

Short answers to the points that usually remain open after the article.

Both can do it. Nginx is leaner and the configuration for proxies shorter, which is why it is the standard today.

No, subdomains are enough: app.your-domain.de, cloud.your-domain.de. Each gets its own certificate.

Yes. Containers publish their ports on 127.0.0.1, Nginx on the host forwards. Alternatively the proxy itself runs as a container, e.g. Traefik or Nginx Proxy Manager.

Yes, a reverse proxy with a few services also runs on an LXC vServer. For Docker behind it take the KVM root server.