19 minutes ago, SMCSUser said:

Correct, go to Apps tab type Wordpress and set it up from there. You do not need Nginx separately. 

Dear Lord I needed you about 4AM last night!!!!!!

 

Thank You So Much!!!!!!

 

it took me less than 5 minutes to get everything working!!

 

I love this community because of people like you.

 

Vic

You are very welcome, glad it worked out for you! Totally agree on the community, without it we would waste endless hours on the easiest tasks, but not knowing about those tasks is what makes it harder lol

@saarg I was curious has there been any discussion on an option for PHP 8 versus 7.4? I wanted to start testing it out safely without impacting the rest of my containers. Thanks in advance!

On 10/29/2021 at 4:17 AM, xaositek said:

@saarg I was curious has there been any discussion on an option for PHP 8 versus 7.4? I wanted to start testing it out safely without impacting the rest of my containers. Thanks in advance!

Not that I know.

some www/ files hidden over network - might be a general Unraid thing, but we'll see...

 

I'm developing a site in appdata/nginx/www from a windows box, and occasionally files and folders that I can see on Unraid are not visible through smb.  EG, /appdata/nginx/www/assets/internal/js/scripts.js is not visible over the network, but another js file in that folder is.

 

If I try and recreate the file from Windows, I get a message saying it already exists, but I can't see it to open and edit it.

 

Any ideas?

On 11/5/2021 at 12:13 PM, saarg said:

Not that I know.

Looks like we migrated to PHP 8 today.

On 8/22/2022 at 5:54 PM, xaositek said:

Looks like we migrated to PHP 8 today.

I'm assuming that this is the reason that none of my websites are accessible today. Any ideas how to fix it?

*EDIT* Disregard. Fixed it. Appears that the new version of Nginx requires Conf files to have the .conf extension or it won't load them.

 

Edited August 23, 20223 yr by NeoDude

1 hour ago, NeoDude said:

I'm assuming that this is the reason that none of my websites are accessible today. Any ideas how to fix it?

*EDIT* Disregard. Fixed it. Appears that the new version of Nginx requires Conf files to have the .conf extension or it won't load them.

 

Thank you!

Adding '.conf' extension to the configuration files helped me solve it quickly.

Ran into an odd issue where websites would get a 502 Gateway error after today's rebase to Alpine 3.17. The following error will fill the logs:

nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

 

Ending up figuring out you can do the following, then restart your Container and it'll fix it.

ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/

mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/

 

I did open https://github.com/linuxserver/docker-nginx/issues/87

Edited January 10, 20233 yr by xaositek

thanks for the fix. Worked for me. Deleting and rebuilding the docker didn't fix it.

mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/

On 1/11/2023 at 1:40 AM, xaositek said:

Ran into an odd issue where websites would get a 502 Gateway error after today's rebase to Alpine 3.17. The following error will fill the logs:

nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

 

Ending up figuring out you can do the following, then restart your Container and it'll fix it.

ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/

mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/

 

I did open https://github.com/linuxserver/docker-nginx/issues/87

Thanks for the help! It worked for me.

Seems that the images were rebuilt on Thursday, but saw it only after applying your fix.

On 1/10/2023 at 3:40 PM, xaositek said:

Ran into an odd issue where websites would get a 502 Gateway error after today's rebase to Alpine 3.17. The following error will fill the logs:

nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

 

Ending up figuring out you can do the following, then restart your Container and it'll fix it.

ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/

mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/

 

I did open https://github.com/linuxserver/docker-nginx/issues/87

 

Thank you for this. I woke up to my websites not working and this fixed the issue. 

So NGIX has failed a few times over the last couple of days ... same error as before

 

Quote

nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3

 

I had to run the commands posted above to get NGIX to work again. Does anyone know how to get this work so we are not constantly having to do this? 

Edited January 20, 20233 yr by SiRMarlon

having same same stream error, worked thanks for the commands but does seem temporary fix

Agreed, the above steps solved the problem for a short time, but the issue returned.

For those having issues with the stream error, check your Swag logs and it will tell you which config files need to be updated. Most likely you need to update your nginx.conf and ssl.conf files using the new sample files in appdata. That fixed the issue for me.

On 1/26/2023 at 4:40 AM, emeybee said:

For those having issues with the stream error, check your Swag logs and it will tell you which config files need to be updated. Most likely you need to update your nginx.conf and ssl.conf files using the new sample files in appdata. That fixed the issue for me.

Same, only required to do ot with nginx.conf tho, not ssl.conf.

For reference for other people, is is how the warning looks like in Swag log:

I shut swag down and replaced the .sample with .conf and its working again

For those of you who have this issues, it cropped up on mine again. The way I fixed this was to backup my sites, and wipe and reinstall NGINX completely. Once I did that and reload my sites the error was gone.