PilotReelMedia Posted Wednesday at 09:56 PM Share Posted Wednesday at 09:56 PM 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 Quote Link to comment
XceRpt Posted yesterday at 03:25 AM Share Posted yesterday at 03:25 AM Having issues with reverse proxy as well after i just updated dockers& plugins. Same " stream" message in my log. Quote Link to comment
PilotReelMedia Posted yesterday at 04:04 AM Author Share Posted yesterday at 04:04 AM 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. Quote Link to comment
Solution Alemiser Posted yesterday at 04:18 AM Solution Share Posted yesterday at 04:18 AM 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 2 Quote Link to comment
PilotReelMedia Posted yesterday at 04:26 AM Author Share Posted yesterday at 04:26 AM I'll give it shot in the morning. Thanks for your solution.. I'll post if it resolves my issue.. Quote Link to comment
in_trauma Posted 23 hours ago Share Posted 23 hours ago 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! Quote Link to comment
caplam Posted 20 hours ago Share Posted 20 hours ago thank you i had the same problem Quote Link to comment
Richamc01 Posted 18 hours ago Share Posted 18 hours ago 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! Quote Link to comment
PilotReelMedia Posted 16 hours ago Author Share Posted 16 hours ago Excellent! Thanks so much. Worked like a charm! Quote Link to comment
Recommended Posts
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.