Linux – Preventing other applications from binding to port 80 and 443

I don't believe you can pass a redirect using a 503 as it's not intended for redirection.

You'll either need to host that specific file in a safe location so it's unaffected by whatever maintenance system is in effect, or use a proxy_pass so that nginx fetches the page from amazon and then passes it on to the client.

Something along these lines might do the trick. Haven't touched nginx in a while, but this might give you an idea of what I'm suggesting:

    error_page 503 @maintenance;
    location @maintenance {
            rewrite ^(.*)$ /maintenance.html break;
            proxy_pass http://mysite.s3-website-us-east-1.amazonaws.com;
    }

Edit: On the page referenced about Google's recommendation for a 503, someone commented a fantastic idea for how to redirect with a 503. He mentioned it for Apache, but the concept is the same with nginx:

Hi!

This might help. On Apache Servers, it's usually not possible to redirect a user with any other HTTP Status Code than of the 3xx class.

Users that visit a site under maintenance deserve to get a useful information page.

Do this with a 302 redirect first that leads to a 503 page that outputs the 503 header (i.e. via PHP or Perl). This will work fine with Google since Google will assign all target page properties to the source page when they encounter a 302 - including the header response. I've tested this on Virtual Hosts and it works as desired. If you can, choose a time with few requests for the service actions.

Regards, Thomas

Seems i have been able to make it works, following these steps :

Install packages : deluge deluge-webui deluged

Then start deluge-web :

# deluge-web or # deluge-web --fork to have it running in background

Then setup NGinx like this :

server {
   listen       80;
   server_name subdomain.example.com;

  location / {
     proxy_pass http://192.168.0.47:8112; # IP Address of your Server 
  }
}

For https (port 443), first i've setup deluge to use https :

• I've create a self-signed certificate following instructions here (step One to Four)
• Then, following this, i've copied server.crt and server.key in $HOME/.config/deluge/ssl

• Open $HOME/.config/web.conf and setup like this :

  "pkey": "ssl/server.key",
  "cert": "ssl/server.crt",
  "https": true,
  

• Then restart deluge-web

• Finally setup NGinx :

  server {
     listen       443;
     server_name subdomain.example.com;
     ssl on;
     ssl_certificate /etc/nginx/ssl/server.crt;
     ssl_certificate_key /etc/nginx/ssl/server.key;
  
     location / {
       proxy_pass https://192.168.0.47:8112; # IP Address of your Server
     }
  }
  

Note that it seems you cannot use deluge with both http and https : you have to choose one or another.