Sorry I feel very stupid but I can't figure it out. When I try to create a named-based virtual host, it tells me the port is already used, which I guess it's picking up from the Docker container of the destination app.
Don't worry about it.
So the idea is this. You want to get to your subdomain.domain.com location that will present some content right?
That content is placed on your NAS, so the idea is to host that content using WebStation on a custom, non-used port of your choice. It doesn't matter what port it is internally (on your NAS). That port will be used with your reverse proxy that will eventually push that content back on 443/https.
So it would like like this:
Internet request > subdomain.domain.com:443 (this is your reverse responding) > virtualhost on NASIPaddress:customport
To make this work, create a virtual host that will point to your content on your NAS and simply apply it a custom port:
As you can see on this image, you can apply a custom HTTP (or HTTPS if you want, but no need if you will push it via reverse later on), and select the document root of your app (this web/web_images is just an example).
Now that you have your app fixed on a custom port, this app is accessible on
The next and final step is to create a reverse proxy for this. So create a RP entry like this:
So as a result you have a subdomain.domain.com URL pointing to your NAS:customport location.