February 22, 20251 yr Hi Need some help with this - I am trying to bring up Nextcloud docker with tailscale option turned on and it does not work. The error that I see in the logs are: Quote GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 30.0.6-ls369 Build-date: 2025-02-18T11:51:25+00:00 ─────────────────────────────────────── using keys found in /config/keys Initializing nextcloud 30.0.6.2 (this can take a while) ... Setting permissions Initializing finished [custom-init] No custom files found, skipping... [ls.io-init] done. 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) I tried changing the listen port in the advanced option of the container but it doesn't seem to take that. Is there anything I am missing here? I can't run anything on 443 as it is taken. Quote #netstat -punta |grep 443 | grep LISTEN tcp 0 0 100.93.197.115:443 0.0.0.0:* LISTEN 13105/nginx: master tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 13105/nginx: master tcp 0 0 192.168.1.10:443 0.0.0.0:* LISTEN 13105/nginx: master tcp6 0 0 ::1:443 :::* LISTEN 13105/nginx: master tcp6 0 0 fd7a:115c:a1e0::ef0:443 :::* LISTEN 13105/nginx: master
February 25, 20251 yr On 2/22/2025 at 4:57 PM, Pentatonic said: Is there anything I am missing here? I can't run anything on 443 as it is taken. This is the wrong approach, at least to me. It would be better to not change the Serve port for Tailscale instead disable 443 in the Nextcloud Apache or nginx configuration in the container or better speaking disable port 80 and change 443 to 80 in the default site config from nginx.
March 1, 20251 yr Author Thank you for your reply. I am not sure how to make that change. Edit the docker config file for Nextcloud? I did change the webUI port for Nextcloud from 443 to something else. That didn't help either.
March 1, 20251 yr Author I changed the nextcloud nginx site-confs from the appdata which gets mapped in the docker config folder. Listen port was changed to something other than 443. This didn't help but got rid of the original error of unable to bind to the port. Now it says a 502 gateway error when accessing via tailscale webUI.
March 1, 20251 yr 2 hours ago, Pentatonic said: I did change the webUI port for Nextcloud from 443 to something else. That didn't help either. Yes, that won't help. 2 hours ago, Pentatonic said: nginx site-confs from the appdata which gets mapped in the docker config folder That's the correct file. 2 hours ago, Pentatonic said: Listen port was changed to something other than 443. This didn't help but got rid of the original error of unable to bind to the port. Now it says a 502 gateway error when accessing via tailscale webUI. You should disable or better speaking comment the whole section (each line with # ) for port 80 and change the 443 section for https from port 443 to 80 and comment the line that pulls the ssl.conf <- since this is handled by Tailscale so that it looks like this:
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.