Hi, I'm having issues with SWAG communicating outside of my server. I have it set as a serve and have the use tailscale option selected. The errors I've getting are these below. How can i fix this?

 

nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)
nginx: [emerg] bind() to [::]:443 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)
nginx: [emerg] bind() to [::]:443 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)
nginx: [emerg] bind() to [::]:443 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address in use)
nginx: [emerg] bind() to [::]:443 failed (98: Address in use)
nginx: [emerg] still could not bind()

 

8 hours ago, tDames said:

How can i fix this?

You have to disable the 443 listener from Nginx since Tailscale is using Serve on port 443 and is handling the certifications and so on.

 

I attached a example configuration for SWAG, may I ask why you even want to do that?

Usually it should be enough to expose container per container in your Tailnet and everything is handled through Tailscale.

 

Here is the example configuration, it belongs in .../swag/nginx/site-confs/default.conf

default.conf

13 hours ago, ich777 said:

You have to disable the 443 listener from Nginx since Tailscale is using Serve on port 443 and is handling the certifications and so on.

 

I attached a example configuration for SWAG, may I ask why you even want to do that?

Usually it should be enough to expose container per container in your Tailnet and everything is handled through Tailscale.

 

Here is the example configuration, it belongs in .../swag/nginx/site-confs/default.conf

default.conf 2.63 kB · 2 downloads

 

I used Spaceinvaders tutorial before tailscale was integrated into unraid to get swag on my tailscale separated from my NGINXProxymanager because I wanted anything i configured in SWAG to be behind tailscale and NPM to be public. If there is an easier way to do it, I can switch it around. I tried the new config and it still gives me the same error. i almost want to reinstall swag as a whole since I used the old method

12 hours ago, tDames said:

i configured in SWAG to be behind tailscale

You can of course do that but why do you want to do that? The main goal of Tailscale is so that you don't have to do that and have your own private network which is available through Tailscale and the individual subdomains that you specify for each container.

 

I would recommend that you configure each container as it's own machine with it's own machine name either through the Unraid Docker Tailscale Integration or TSDProxy and then you should be able to reach your container through your Tailnet with SSL, their machine names and your Tailscale Domain.

As a follow-up to this discussion. I have a similar issue when enabling Tailscale within the SWAG docker container and using Docker MODS. When enabling the Tailscale integration directly in the container, the container can no longer access the DNS records for lscr.io.

The use case for this would be to allow subdomain access via tailscale only as the A Record resolves to a 100.x.x.x tailscale ip and also have externally facing reverse proxy. This is similiar to SpaceInvaderOnes Uncast Ultimate SWAG on Unraid walkthrough (https://www.youtube.com/watch?v=3uW97tXYWVI)

It seems like it is an issue with the port that tailscale inside the docker container uses is 443. Is there a way to solve this?