• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

504 Gateway timeout after php settings changes

Edi Duluman

Basic Pleskian
Hello guys ! This has happened to me twice now, once yesterday, once today.

I'm not really sure ( will try again later and will come in with an update ) but yesterday I had no clue what happened. So the server is all working fine, I go into Plesk, do some PHP performance settings, change the upload maximum size value, ( you can do whatever setting you want ).

The expected behaviour is the server will restart it's services so PHP settings take place, and then everything should be back to normal after the sync is finished.

What happens instead is that while Plesk dashboard is fine, the websites are not working anymore, you get a nginx 504 gateway timeout.

uk1goRv.png


I didn't know what caused that first time but the second time, only thing I did was this, I'll try again in a few. The "workaround" for this issue is to reboot the server from within the dashboard, then everything is fine again.


LATER EDIT:
I have just changed some permissions for a subscription plan, it finished syncing, again, the websites return a gateway timeout. Restarted server again, worked wonders. Must be some service not working properly ( I thought it may be php servers, restarted them , does not do anything, will try restarting the apache next time, see if it has any impact ).
 
Last edited:
Back
Top