January 25, 20233 yr Last swag docker update caused a issue with my ability to published my instance of nextcloud out to my duckdns subdomain. On swag boot I get the initial repot in the log: **** The following active confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare the following files to the samples in the same folder and update them. **** **** Use the link at the top of the file to view the changelog. **** ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐ │ old date │ new date │ path │ ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤ │ 2020-10-04 │ 2022-08-16 │ /config/nginx/nginx.conf │ │ 2020-06-02 │ 2022-08-20 │ /config/nginx/ldap-server.conf │ │ 2020-05-31 │ 2022-09-22 │ /config/nginx/authelia-server.conf │ │ 2020-05-31 │ 2022-08-20 │ /config/nginx/authelia-location.conf │ │ 2020-10-29 │ 2022-08-20 │ /config/nginx/ssl.conf │ │ 2020-10-04 │ 2022-09-01 │ /config/nginx/proxy.conf │ │ 2020-12-09 │ 2022-10-28 │ /config/nginx/proxy-confs/nextcloud.subdomain.conf │ │ 2021-01-03 │ 2022-10-03 │ /config/nginx/site-confs/default.conf │ └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘ [custom-init] No custom files found, skipping... [ls.io-init] done. Server ready Then I get a spamming message in the log : 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 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 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 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 local port still works but the subdomain just times out. Can anyone help me? Thanks. Version 6.11.5
January 26, 20233 yr Having issues with reverse proxy as well after i just updated dockers& plugins. Same " stream" message in my log.
January 26, 20233 yr Author Thanks for saying so. Always nice to know you are not alone. I think the update came from a different repository and will require adjustments for it to work the way the old one did. I spent a day trying to fix it and I'm done.
January 26, 20233 yr Solution This is what i did to fix it. Stop Swag docker Go to \\<server>\appdata\swag\nginx folder rename original nginx.conf to nginx.conf.old copy nginx.conf.sample to nginx.conf rename ssl.conf to ssl.conf.old copy ssl.conf.sample to ssl.conf restart swag docker This worked for me
January 26, 20233 yr Author I'll give it shot in the morning. Thanks for your solution.. I'll post if it resolves my issue..
January 26, 20233 yr 4 hours ago, Alemiser said: This is what i did to fix it. Stop Swag docker Go to \\<server>\appdata\swag\nginx folder rename original nginx.conf to nginx.conf.old copy nginx.conf.sample to nginx.conf rename ssl.conf to ssl.conf.old copy ssl.conf.sample to ssl.conf restart swag docker This worked for me This worked for me! Thank you!
January 26, 20233 yr 9 hours ago, Alemiser said: This is what i did to fix it. Stop Swag docker Go to \\<server>\appdata\swag\nginx folder rename original nginx.conf to nginx.conf.old copy nginx.conf.sample to nginx.conf rename ssl.conf to ssl.conf.old copy ssl.conf.sample to ssl.conf restart swag docker This worked for me I had the same issue. This worked for me. Thank you!
January 28, 20233 yr You can also just comment out the next line: include /etc/nginx/conf.d/*.conf; like so: # include /etc/nginx/conf.d/*.conf; inside your nginx.conf file. (or just delete the line completely) The only file inside /etc/nginx/conf.d/ folder is the stream.conf file. I think this is better because there are some custom values added in the nginx.conf that are gone in the nginx.conf.sample file. An alternative is going into the console of the Swag Container and do the following: ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/ mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/ Source: Edited January 28, 20233 yr by Smoetzak
January 29, 20233 yr On 1/26/2023 at 5:18 AM, Alemiser said: This is what i did to fix it. Stop Swag docker Go to \\<server>\appdata\swag\nginx folder rename original nginx.conf to nginx.conf.old copy nginx.conf.sample to nginx.conf rename ssl.conf to ssl.conf.old copy ssl.conf.sample to ssl.conf restart swag docker This worked for me I only did the ngnx.conf and it worked, did not touch ssl.conf, and it worked. Thanks! Edited January 29, 20233 yr by Mihle
January 30, 20233 yr YEEESSSSS!!!! Thank you soooooo much! Finally have my nextcloud back! Thaaaaannnkkkkk yoouuuuuu!
January 31, 20233 yr Thanks guys. Still having trouble with geoip2. Unknown directive error confirm/../geoip2 Edited January 31, 20233 yr by bluesky509
February 28, 20233 yr It didn't work for me though... I'm wondering if it's something from my server, cause I stopped the swag container and started one NPM container I had working a few weeks ago for testing and it's the same. I mean, the log console it's ok, but I get a 552 error when I'm trying to connect to any of my services.
March 16, 20233 yr On 1/26/2023 at 6:18 AM, Alemiser said: This is what i did to fix it. Stop Swag docker Go to \\<server>\appdata\swag\nginx folder rename original nginx.conf to nginx.conf.old copy nginx.conf.sample to nginx.conf rename ssl.conf to ssl.conf.old copy ssl.conf.sample to ssl.conf restart swag docker This worked for me Amazing man, I suspected something had changed in the updated and my config was old. This saved me a ton of debugging!
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.