[BUG] Dies if served in any port other than 443

[VentGrey]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Launching a container mapped in any port other than 443 does bring up the container, and nothing seems to fail. Until you look at the logs and see the endless sea of NGINX log spam:

nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3

No further information is given, neither in the official NextCloud Image nor the LinuxServer.io wiki page.

There is a post in the NextCloud forums but it got a nearly useless answer.

Expected Behavior

Going to the provided URL+Port and see the setup screen.

Steps To Reproduce

1. In both Docker/Podman on Debian.
   • I'm aware that podman is not officially supported.
2. Use the official instructions from the linuxserver wiki.
3. Change -p 443:443 to anything else like: -p 4000:443 or -p 3009:443
4. Start your container
5. Emit an SSL cert for your HTTPS Url
6. Go to the Url
7. :upside_down_face:

Environment

- OS: Debian Bookworm
- How docker service was installed: Official Repositories.

CPU architecture

x86-64

Docker creation

docker run -d --name="nextcloud" -e PUID=1006 -e PGID=1006 -e TZ=Etc/UTC -v /containers_one/nextcloud/config/:/config -v /containers_one/nextcloud/data/:/data -p 6008:443 --restart=always lscr.io/linuxserver/nextcloud:latest

Container logs

nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3
nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3
nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3

...ad infintum.

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[VentGrey]

Solved patching apache manually.