Article ID: 127697, created on Dec 5, 2015, last review on Sep 21, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux


Plesk GUI is inaccessible with error 504 gateway timeout (nginx)


Plesk upgrade/update stuck at this stage for a long time:

 ===> Plesk database scheme upgrade has been completed


===> Cumulative upgrade of Plesk (final stage) has been completed.

In ps auxf utility output it is possible to find this string or something similar that is not changing for a long time:

\_ /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/plib/Upgrade/upgrade.php

After killing this process, upgrade can be continued or it hangs again.

It may be not possible to login to Plesk - login page is blank.

Running Plesk autoinstaller again may result in halt at this place:

 gpg-pubkey-c105b9de-4e0fd3a3 gpg(CentOS-6 Key (CentOS 6 Official Signing Key) <c
 gpg-pubkey-914bdf7e-55c05220 gpg(Plesk Team <>)


Ign all/all Translation-en
Ign trusty/all Translation-en
Fetched 221 kB in 3s (57.1 kB/s)
Reading package lists...
ERROR: Interrupted by user
Reading package lists...

Command plesk repair installation and other Plesk related commands may also stuck.


This is a software issue with internal ID PPPM-3717. The fix will be included in further Plesk updates.


As workaround, remove lock_manager temporary files:

# rm -f /usr/local/psa/var/cache/SharedLockManagerStorage*

Restart services:

# service sw-engine restart && service sw-cp-server restart

Run Plesk installer and continue upgrade. Execute plesk repair installation if it is required.

Search Words

Error: Service node is unknown for sysuser with id=0

repair stuck

vzpkg update erroe

trusty all Translation

gpg-pubkey-914bdf7e-55c05220 gpg(Plesk Team <>)

plesk blank page

plesk upgrade stuck

bootstrapper stuck

plesk 12.5 blank page

Access to controll panel

plesk installer does not start


plesk 12.5 upgrade stuck

unable to login Plesk

Plesk task hang

504 Gate Timeout

trusty/all Translation-en

Plesk inaccessible

504 gateway timeout

742559b1631652fadd74764ae8be475e 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 e335d9adf7edffca6a8af8039031a4c7 2a5151f57629129e26ff206d171fbb5f

Email subscription for changes to this article
Save as PDF