-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prestashop 8.1 FPM with Nginx - 504 Gateway Timeout #352
Comments
I just realised my nginx.conf was completely wrong. Now that I fixed it, I can access the Prestashop installer correctly, but the original issue with the 504 Gateway Time-out that I had running the Apache image, occurs with the FPM setup too. I've updated the title of this issue to match my problem correctly. Everything runs well until Prestashop wants to install the theme. Both Apache and FPM images spits 504 Gateway Time-out error. Running Docker on M2 Macbook Pro 2023. Ventura 13.4.1 Log:
Updated nginx.conf for reference:
|
I got it working after adding this
|
Yup, it worked, but I get error 500 now when using the GUI web installer. Installing via CGI worked, and I was able to install. |
Hi,
I am trying to get Prestashop 8.1 running on Docker as my dev environment, but I can't succeed. First I tried the prestashop:latest image with Apache web server and used Nginx as a SSL Proxy to run it over HTTPS. Everything worked fine until the Theme Installation step in the installer; I was getting 504 Gateway Time-out error. Running it just on Apache without Nginx didn't helped. Tried setting the proxy timeout limits to a higher value, still no luck.
I've decided to use FPM image instead. Now the Prestashop's docker log says that the FPM is listening for connections, my nginx server seems to be configured correctly, everything's up, but I get the 502 Bad Gateway error trying to open the installer via localhost in my browser...
Can someone help me with this one?
Docker log:
My docker-compose.yml:
I have all my .env values in correctly. "PS_DOMAIN" is set to "localhost".
nginx.conf:
The text was updated successfully, but these errors were encountered: