Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
I just had updated to mailenable 1.9, after that I cannot login to control panel and webmail doesn't work either. Accessing control panel, it ask as always if I wish to continue after the certificate issue, and then it just waits and waits and waits and nothing happens.
It maybe a port problem? if so? how and where should I look?
So I went to IIS, websites, webmail(default) properties and changed TCP port from 8425 to 9998 and then had reset the server.
Now control panel works again and also all my domains webmail.!!
It should not be the reason of the problem because 9998 port is port for SmarterMail and not for Horde. It seems that you had to restart your server after upgrade.
I already had restarted the server, and the problem was the same. Only when I had changed this port it started to work.
Now I got other problems, looking at the server log, suddenly I got many errors from memailfilter.exe until mail and http server stops to work anymore, then I must restart. I think that after upgrading mailenable you must do some arragements on it's configuration so it can works well with Plesk, related to Spamassasin.
All this problems started when I had upgraded to 7.5.4!!! Before that I was happy! Just after this upgrade the server started to have DNS problems and also mail problems. So I decided to upgrade mailenable, then the control panel and webmail didn't worked. Now I get this error:
What is error of memailfilter?
As for "client 217.126.110.29#1638: update 'domain.com/IN' denied" I think that somebody tried to update DNS record of that domain and it was unsuccessfully