Is there an existing issue for this?
Name of mod
swag-dbip
Name of base container
swag
Linuxserver.io version: 4.1.1-ls391
Build-date: 2025-06-21T03:49:18+00:00
Current Behavior
This line in dbip.conf crashes SWAG
MN no;
[emerg] 833#833: conflicting parameter "mn" in /config/nginx/dbip.conf:108
mn is for Mongolia.
While commenting it solves the issue.
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Changes to nginx config detected and the changes are valid, reloading nginx
Expected Behavior
It didn't happen before.
Steps To Reproduce
in portainer 2.27.7
update the stack
container doesn't get created
Environment
- OS: DSM 7.2.2
- How docker service was installed: Synology package
CPU architecture
x86-64
Docker creation
services:
swag:
container_name: swag
image: linuxserver/swag:latest
#version: 4.1.1-ls391
cap_add:
- NET_ADMIN
environment:
- VALIDATION=dns
- DNSPLUGIN=
- URL=************
- SUBDOMAINS=wildcard
- ONLY_SUBDOMAINS=false
- DOCKER_MODS=linuxserver/mods:swag-dashboard|linuxserver/mods:swag-crowdsec|linuxserver/mods:swag-dbip
- CROWDSEC_API_KEY=************
- CROWDSEC_LAPI_URL=http://crowdsec:8080
# APPSEC Component /docker/swag/crowdsec/crowdsec-config/acquis.d/appsec.yaml
# /docker/swag/config/crowdsec/crowdsec-nginx-bouncer.conf
- CROWDSEC_APPSEC_URL=http://127.0.0.1:7422
- SWAG_AUTORELOAD=true
- SWAG_AUTORELOAD_WATCHLIST=/config/nginx/proxy-confs|/config/keys
volumes:
- /volume1/docker/swag/config:/config
#Fail2BAN
- /var/log/auth.log:/log/host_ssh_auth.log:ro
- /volume1/docker/nextcloud/data/nextcloud.log:/nextcloud/nextcloud.log:ro
- /volume1/docker/swag/config/fail2ban/fail2ban.sqlite3:/dashboard/fail2ban.sqlite3:ro
ports:
- 443:443
security_opt:
- no-new-privileges:true
restart: unless-stopped
Container logs
nginx: [emerg] conflicting parameter "mn" in /config/nginx/dbip.conf:108
nginx: configuration file /etc/nginx/nginx.conf test failed
Changes to nginx config detected but the changes are not valid, skipping nginx reload. Please fix your config.
Is there an existing issue for this?
Name of mod
swag-dbip
Name of base container
swag
Linuxserver.io version: 4.1.1-ls391
Build-date: 2025-06-21T03:49:18+00:00
Current Behavior
This line in dbip.conf crashes SWAG
MN no;[emerg] 833#833: conflicting parameter "mn" in /config/nginx/dbip.conf:108mn is for Mongolia.
While commenting it solves the issue.
Expected Behavior
It didn't happen before.
Steps To Reproduce
in portainer 2.27.7
update the stack
container doesn't get created
Environment
CPU architecture
x86-64
Docker creation
services: swag: container_name: swag image: linuxserver/swag:latest #version: 4.1.1-ls391 cap_add: - NET_ADMIN environment: - VALIDATION=dns - DNSPLUGIN= - URL=************ - SUBDOMAINS=wildcard - ONLY_SUBDOMAINS=false - DOCKER_MODS=linuxserver/mods:swag-dashboard|linuxserver/mods:swag-crowdsec|linuxserver/mods:swag-dbip - CROWDSEC_API_KEY=************ - CROWDSEC_LAPI_URL=http://crowdsec:8080 # APPSEC Component /docker/swag/crowdsec/crowdsec-config/acquis.d/appsec.yaml # /docker/swag/config/crowdsec/crowdsec-nginx-bouncer.conf - CROWDSEC_APPSEC_URL=http://127.0.0.1:7422 - SWAG_AUTORELOAD=true - SWAG_AUTORELOAD_WATCHLIST=/config/nginx/proxy-confs|/config/keys volumes: - /volume1/docker/swag/config:/config #Fail2BAN - /var/log/auth.log:/log/host_ssh_auth.log:ro - /volume1/docker/nextcloud/data/nextcloud.log:/nextcloud/nextcloud.log:ro - /volume1/docker/swag/config/fail2ban/fail2ban.sqlite3:/dashboard/fail2ban.sqlite3:ro ports: - 443:443 security_opt: - no-new-privileges:true restart: unless-stoppedContainer logs