You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After update 1.32.0-ls173 last night I've been thrown the following error in the logs: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
This results in my swag container not starting.
Expected Behavior
No response
Steps To Reproduce
I'm using 2.2.0-ls174 now and it's still behaving the same
Environment
- OS: Ubuntu 18.04.6
- How docker service was installed: distro's packagemanager
CPU architecture
x86-64
Docker creation
Docker Compose:
# SWAG – SWAG including Nginx and PHP
swag:
image: "linuxserver/swag"
hostname: swag
container_name: "swag"
volumes:
- /opt/docker/swag/config:/config
ports:
- 443:443
# Only for validation, redirect all http traffic to https in config
- 80:80
restart: always
environment:
- PUID=***
- PGID=***
- TZ=***
- EMAIL=***
- URL=***
- EXTRA_DOMAINS=***
- SUBDOMAINS=wildcard
- VALIDATION=dns
- DNSPLUGIN=cloudflare
networks:
swag:
ipv4_address: 192.168.1.2
Container logs
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
After update 1.32.0-ls173 last night I've been thrown the following error in the logs: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
This results in my swag container not starting.
Expected Behavior
No response
Steps To Reproduce
I'm using 2.2.0-ls174 now and it's still behaving the same
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: