• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

webmail broken

kram@

Regular Pleskian
Hi All,

Just ran the update and now webmail does not load.
When i enter webmail.domain.co.za it returns the default page of the default domain.
 
Hello,

First of all, I suggest you to check current Plesk package and Plesk database version:
# rpm -q psa
# cat /usr/local/psa/version
# mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa -e "select * from misc where param='version'"

Normally, you have to see 8.3 version. If it is not so, it means that upgrade was failed for some reasons, check Plesk autoinstaller log to get exact cause:
# less /tmp/autoinstaller3.log

If everything looks fine, reconfigure Webmail virtual host:
# /usr/local/psa/admin/sbin/websrvmng -a -v

Hope, it will help you to eliminate this issue.
 
Hi Mark:

Most likely, this is a DNS related issue. If you have created the domain only recently, a certain time spell should pass for the propagation of nameservers to occur. Can youi check if the domain webmail.domain.bla.bla is resolved from outside? Also try adding "ip.ip.ip.ip domain.bla.bla" into your /etc/hosts file, and see what will browser tell you for the webmail.domain.blah.bla page..
If you still be no wiser, try running the command to reconfigure the webserver for your domain:
/usr/local/psa/admin/sbin/websrvmng --reconfigure-vhost --vhost-name=domain.bla.bla

Finally, you then check if selinux is enabled in the system:
# getenforce
If it is 'Enabled' or enforcing , try switching it into 'permissive' mode:
# setenforce 0
(and if you will need to turn SELinux off permanently, edit file /etc/sysconfig/selinux and set SELINUX variable to 'disabled').

Hope this helps a byte.
 
did you see any errors during the upgrade ?

can you post some of the logs?
 
Back
Top