• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Error installing Dovecot, now 502 Bad Gateway on server

Shawn1

New Pleskian
Hello,

I tried to install Dovecot on my server and move away from Courier IMAP... But when I try to install in Plesk Installer I get the following errors... What are my options? :-\

Now I also cannot go to view my home in my control panel... I get...
502 Bad Gateway
nginx

My websites still work. I have not tested my email.

Help please? :(

I am running CentOS 6.5... and Plesk 12 but not sure of exact version of Plesk 12.

I had to upload file because error is over 10,000 chars.
 

Attachments

  • error.txt
    27.2 KB · Views: 2
I restarted server via SSH and the 502 Bad Gateway issue has been resolved.

I can also send email outbound... but now emails are not delivered :( Nor do I receive a bounce back. I will wait a bit maybe server is overloaded restarting.
 
Email working again after going back to Courier IMAP... Send/receive OK...

I believe I have a PHP issue relating to tables... I believe my server host 1and1 tried to update PHP many months ago but never finished upgrade and tables need upgrading/repair?
 
Hi Shawn1,

did you read the sticky thread and it's suggestions?


To your error - log:
Code:
warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID 4520afa9: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
Fatal error during packages installation: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.
YumBaseError: The GPG keys listed for the "CentOS / Red Hat Enterprise Linux 6 - atomicrocketturtle.com" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.

Did you notice this warning and did you try to solve this issue first?

https://atomicorp.com/forums/viewtopic.php?t=7591&p=40937

https://atomicorp.com/forum/viewtopic.php?t=6385&p=38888


Consider to re-run bootstrapper repair, after you solved your issue, please.


 
Back
Top