Nipun Shakya
New Pleskian
Hello everyone. i just purchased Plesk from shop.ohodomain.com.
After updating my Plesk from 11 to Plesk 12.5.30, I am unable to access https://162.251.81.127:8443/ I get the error message of "403 Forbidden nginx" and now I am unable to access my Plesk Panel.
Here's what I did:
1. Followed
http://docs.plesk.com/en-US/12.5/ad...ver-administration/distupgrade-support.74627/
to upgrade Plesk to 12.5.30 which completed successfully.
2. The Plesk Panel would show up Ubuntu 14.04.4 updated upon checking Plesk Panel.
3. Updated my Apache2 as it as stopped working.
4. However, logging into https://162.251.81.127:4643/vz/cp/ would still show ubuntu 12.04-x86_64 as my operating system. But logging in from PuTTY will show that my system is Ubuntu 14.04.4 (CONFUSION HERE)
5. Now I am unable to login to https://162.251.81.127:8443/ with my credentials
I guess after the installation of a package named libxmlrpc-c++3 the system broke down. But it was an automated process and I couldn't do anything about it.
I'm sorry about this but I just started to use VPS since last 12 hours. Some serious assistance is needed here. Any suggestions are warmly welcomed.
After updating my Plesk from 11 to Plesk 12.5.30, I am unable to access https://162.251.81.127:8443/ I get the error message of "403 Forbidden nginx" and now I am unable to access my Plesk Panel.
Here's what I did:
1. Followed
http://docs.plesk.com/en-US/12.5/ad...ver-administration/distupgrade-support.74627/
to upgrade Plesk to 12.5.30 which completed successfully.
2. The Plesk Panel would show up Ubuntu 14.04.4 updated upon checking Plesk Panel.
3. Updated my Apache2 as it as stopped working.
4. However, logging into https://162.251.81.127:4643/vz/cp/ would still show ubuntu 12.04-x86_64 as my operating system. But logging in from PuTTY will show that my system is Ubuntu 14.04.4 (CONFUSION HERE)
5. Now I am unable to login to https://162.251.81.127:8443/ with my credentials
I guess after the installation of a package named libxmlrpc-c++3 the system broke down. But it was an automated process and I couldn't do anything about it.
I'm sorry about this but I just started to use VPS since last 12 hours. Some serious assistance is needed here. Any suggestions are warmly welcomed.