• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved 503 Service Temporarily Unavailable after migrating locked Plesk accounts

unsp

New Pleskian
I am running Plesk 12.5 on a debian server. I migrated all user accounts in locked state from another Plesk Installation. After unlocking all of them, the (Apache) webserver still throws a 503 error when accessing the sites even though they are shown working in plesk. There is only one of 15 user accounts which is not haveng these problems and i only got it to work after restarting apache. For the other sites, the error is still there after restarting apache and rebooting the server. I have no idea why this is happening. Can someone help me?

Solution:
On the old server, accounts were still locked and the DNS updates were delayed for some domains.
 
Last edited:
Back
Top