The only way to do that is for the proxy to divert traffic from the second domain to the IP of the second server. In this case you are using Swag, so you will have to look in the Swag documentation how to configure this, if Swag allows it.
If you can't do it or it is complicated to do, you have the alternative of replacing Swag with Nginx Proxy Manager. https://nginxproxymanager.com/ It has a graphical interface and the configuration is very intuitive. Doing what you want would be very simple.
I would like to be able to configure the 2nd machine so that I can also access it via a 2nd duckdns domain
Not possible since WAN port 80 && 443 is already occupied for SWAG on the 1st machine.
Not possible since WAN port 80 && 443 is already occupied for SWAG on the 1st machine.
mmm You just mean that it is not possible with Swag? With Nginx Proxy Manager it is possible to forward a second domain to a second server.
With Nginx Proxy Manager it is possible to forward a second domain to a second server.
Ok.
Since I don't use it, I have no idea about it.
As for SWAG, when you launch it, you take over port 80 && 443 (only 443 if using duckdns validation on the YML) and it's linked to 1 subdomain.
Doesn't matter which internal port its using.
Of course, you can have gazillion sub-subdomains after by using the wildcard environment.
If you want to add a 2nd domain (or duckdns.subdomain), you need a 2nd SWAG running but the needed WAN ports to call for certificates are already taken, even if you set the internal ports different than the 1st machine.
If NPM can sort this, than it's quite a new info for me.
If NPM can sort this, than it's quite a new info for me.
NPM allows you to configure different certificates for different domains. They do not necessarily have to be subdomains. NPM is responsible for managing each certificate separately with Let's Encrypt (or whatever service). The owner of port 80 and 443 is NPM, it is not a domain.
After that you just have to make sure that the traffic from those different domains reaches the NPM IP. NPM will be in charge of redirecting traffic to each server or service (different IPs) depending on whether the origin is one domain or another and vice versa.
It is very easy to configure, the graphical interface makes it very easy.
just have to make sure that the traffic from those different domains reaches the NPM IP.
NPM will be in charge of redirecting traffic to each server or service (different IPs) depending on whether the origin is one domain or another and vice versa.
I understand how it can/should work.
What I never thought was that the Proxy Server (be it NPM, SWAG, whatever) could translate 2x (or more) names to IPs.
Maybe I need a better understanding on REGEX or whatever its called.
Since I never needed it, never wondered about it, but I can only consider that SWAG will also be able to do this.
[EDIT]
It seems, it is:
SWAG Reverse Proxy, handling multiple domains across multiple servers | WalnutHomelab
[/EDIT]
And more:
swag reverse proxy 2 different domains at DuckDuckGo
What I never thought was that the Proxy Server (be it NPM, SWAG, whatever) could translate 2x (or more) names to IPs.
Actually if you have two containers with two services in Swag you are already doing it. It doesn't matter if they are domains or subdomains, it's the same principle. My question was whether Swag is capable of managing different certificates. I see you have solved it. It was strange that Swag had that limitation.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
