[BUG] NGINX inside the image is badly configured.

[VentGrey]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Same as the NextCloud image the container spams the console with:

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
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
nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3

It's always the same shit with PHP-based + NGINX containers.

Expected Behavior

idk...a working app would be nice.

Steps To Reproduce

1. Pull image from lscr.io/linuxserver/bookstack:latest
2. Deploy via docker run using the recommended port: -p 6875:80
3. Wait for migrations to finish
4. Again, watch an NGINX error in the console.

Environment

- OS: Debian 12
- How docker service was installed: Official Docker Repositories

CPU architecture

x86-64

Docker creation

docker run -d \
  --name=bookstack \
  -e PUID=xxxx \
  -e PGID=xxxx \
  -e TZ=Etc/UTC \
  -e APP_URL=xxxxxxxxxx \
  -e DB_HOST=xxxxxxxxxx \
  -e DB_PORT=xxxxxxxxxx \
  -e DB_USER=xxxxxxxxxx \
  -e DB_PASS=xxxxxxxxxx \
  -e DB_DATABASE=xxxxxxxxxx \
  -p 6875:80 \
  -v ./bookstack/config:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/bookstack:latest

Also tried with --network=host but the result is the same.

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
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
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
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
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
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
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
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
nginx: [emerg] invalid port in resolver "fe80::1%eno1" in /config/nginx/resolver.conf:3

[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.

[Roxedus]

whats the contents of the file?

[VentGrey]

# This file is auto-generated only on first start, based on the container's /etc/resolv.conf file. Feel free to modi>

resolver  10.0.2.3 <local-ip-here> fe80::1%eno1 valid=30s;

The way to patch it manually in case anyone is interested:

1. Log into the contaner: docker exec -it bookstack /bin/sh
2. Edit the file vi /config/nginx/resolver.conf and replace whatever that fe80-something is with the correct container port defined in -p
3. Reload NGINX gracefully with nginx -s reload

• Sometimes nginx refuses to reload. Seding a kill -HUP <pid> does the trick.

This only happens in PHP/NGINX containers. Either autogen is doing something fishy or most likely my Network settings are wrong asf.

[Roxedus]

Thanks, could you also please paste the contents of /etc/resolv.conf inside the container? This is the code that populates the file in /config.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue is locked due to inactivity