Multiple Servers from One Port on NAS

Have you ever wanted to have a single URL with a standard web port to access all the web services you run on your NAS? Most consumer Network Attached Storage (NAS) devices come with a built-in web server which can be used to share all of your services under one address.


How does this work you might ask? Web servers can route traffic to other servers using what’s called a “Reverse Proxy.” A proxy is a server or device which can act as an intermediary for other devices. In this case, the web server in your NAS can proxy traffic from other web servers on the same machine or even in the network. This allows you to have a single base URL like which you can use for all your traffic. Each of your servers will then either be accessible via a subdomain or path.




In a typical setup, you would open up a port on your router for each and every server or device you want to access outside your network. In this case, your when you setup port forwarding on your network, your router is proxying the connections from outside your network to devices inside your network. The downside with this approach is you need to open a port for each and every server on your network and if any of those devices share the same port, you will only be able to forward traffic for one of the devices or you’ll have to forward a non-standard port.

Additionally, some networks like work or public networks will block non-standard ports. This means that if your server runs on a high port number like 5050 or 8989, it’s possible that this port will be blocked on other networks you might use. Using a reverse proxy, you can use a standard web port which should be open on a normal network (80=http, 443=https).

How-to (QNAP)

In this example, I’ll show how to setup an HTTP Reverse Proxy on a QNAP NAS using the built-in webserver, Apache.

Note: The same general concepts of modifying the Apache configuration file applies to other devices as well, but you may need to find the location of your configuration file.

Update: I have switched from Apache to Traefik as a reverse proxy on QNAP. Updating the built-in Apache configuration on QNAP has become increasingly difficult and the introduction of containers on QNAP has made the use of packages like Traefik much more approachable.

I’ve left the remainder of this blog post available as the concepts from this article apply to using Apache as a reverse proxy on other systems as well.

We will setup a reverse proxy to allow access to the following servers:

To do this, we will start by remoting into our NAS using SSH. If you don’t already have an SSH client, consider using Mobaterm which has an SSH and SFTP client all built into one.

  1. Open your SFTP client and connect to your NAS IP address.
  2. Navigate to /mnt/HDA_ROOT/.config/apache/
  3. Open/Edit your apache.conf file, scroll to the bottom and add the following line:
    Include /share/Web/custom.conf

    Note: You can also include the contents of the custom.conf (below) directly in your apache.conf file, but some NAS devices will completely reset the apache.conf file upon reboot. By using an external file, you can quickly ‘fix’ things after a reboot by adding the single “Include” line.

  4. Save the file and choose ‘Yes’ to upload it back to the NAS
  5. Navigate to /share/Web/ and create a new file called custom.conf
  6. Open/Edit the newly created custom.conf file and add the following details
    #Customizations for reverse proxy
    LoadModule proxy_module modules/
    LoadModule proxy_http_module modules/
    ProxyPass http://localhost:8989/sonarr
    ProxyPassReverse http://localhost:8989/sonarr
    ProxyPass http://localhost:5050/couchpotato
    ProxyPassReverse http://localhost:5050/couchpotato

    Note: The path in the location tag is the path you want to use to access the server. The URL inside the location tag is the current target URL of the server. Also note that some applications will require you to set a ‘Url Base’ in the General/Server advanced settings as shown in the example here for the target URLs.

  7. Save the file and choose ‘Yes’ to upload it back to the NAS
  8. From the SSH interface (right side of Mobaterm), enter the following command and press Enter:
    /etc/init.d/ restart


Congratulations! You’ve now setup your reverse proxy and can access your servers at the desired URLs!






7 responses to “Multiple Servers from One Port on NAS”

  1. ESPe Avatar

    What about ssl?

    1. josh Avatar

      The QNAP HTTP server supports SSL out of the box. This is just setting up the reverse proxy mappings. So if you’ve already setup SSL on the QNAP HTTP server, then you can hit the HTTPS endpoint and these reverse proxy endpoints will work just like they do with HTTP.

  2. Viking Avatar

    Does this mean that it is possible to achieve reverse proxy functionality on any QNAP server without installing a reverse proxy (like i.e. NGINX) ?

    1. josh Avatar

      Yes, the Apache server has reverse proxy capabilities built-in.

      1. Josh Lyon Avatar

        I was just looking back through some comments after migrating my blog and wanted to update this post that the latest versions of the QNAP software have made it increasingly difficult to use the built-in Apache server for reverse proxying.

        I’ve moved all my reverse proxying over to Traefik. It was a bit of effort to get my head wrapped around how their configuration system worked (especially with SSL), but once I got one resource figured out it was easy to duplicate the configuration across other resources.

  3. Alex Avatar

    Hey, care to share how did you do it with Travik? Focusing on the qnap admin gui, mainly.
    I’m struggling with getting it to work behind nginx

    1. Josh Lyon Avatar

      Thanks for posting, Alex! I drafted up a nice long post and lost it before it got posted, so here’s a condensed version.

      I use the official `traefik` container in QNAP’s container station with the Network Mode configured for NAT and three ports mapped: 443, 80, 8080.

      I only expose the SSL enabled port (443) externally and use the others within my network.

      The Traefik configuration file was the biggest challenge for me. The officially posted documentation didn’t seem to line up with the version of Traefik I have installed. Here’s a snippet of my configuration file:

      Edit: The code formatting in comments isn’t working well, so here’s a link to a Github Gist showing a snippet from the Traefik configuration file:

Leave a Reply

Your email address will not be published. Required fields are marked *