Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
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
It's unlikely that somebody will need it now, but anyway - since I'm dealing with the same problem now.
This happens because DrWeb changed packages names in 4.33 - before that there was only drweb package and in 4.33 it was split to three packages - drweb-base, drweb-daemon and drweb-updater...
If you really do not want to accept e-mails over TLS you can set "disable" to "yes" in smtps_psa or just move this file out from /etc/xinetd.d/
don't forget to restart xinetd afterwards
As I understand:
1) If you used regular fixcrio sources with no TLS patch you can only add it to smtp_psa and submission_psa
2) If you patched fixcrio sources with TLS patch then you can use it in smtp_psa, submission_psa AND smtps_psa
Please check my post again - it should be...
and yes, I did mention this topic so your input is as well appreciated!
indeed, Plesk updates are not as frequent as we wish, I hope this will be changed to Virtuozzo policy - monthly updates.
YaserU, omerk, I'm not sure what went wrong in your case. I can only advise to double-check everything and make sure that the compiled binary is OK and can be executed:
Also check permissions/ownership of the binary and if nothing helps - check your maillog, the error output should be there.
I'm not sure how could that happen, because changes in smtp_psa and submission_psa files only affect how qmail receives messages.
are you sure you didn't change anything else? you should probably check your maillog (usually /usr/local/psa/var/log/maillog) for errors.
i have just seen the same issue, but in my case the template was custom and problem was probably in the CSS styles - the site was scaled (magnified) by default. I'm not sure though, the issue is not fixed yet and I don't have any more information.
One more solution suggested on Microsoft support forum - but this requires qmail recompilation:
http://windowslivehelp.com/community/t/123986.aspx
http://www.arctic.org/~dean/patches/qmail-0.95-liberal-lf.patch
thanks for pointing this out, faris! I corrected my post.
of course it breaks TLS, I should have understood that, shame on me! since the data is encrypted fixcrio CR "fix" effectively damages the data.
=========
This is mentioned here:
1) http://iain.cx/ssl/?qmailtls
BIG IMPORTANT...
I can't beleive that I haven't heard of this problem before, but it does really exist. Even more surprising is that it happens not for all hotmail servers - when I tested it I found out that one hotmail account was OK, but the other one could not send e-mail to Plesk.
And I can confirm that...
Let me explain, just in case anyone else has this problem (though it's unlikely cause I think it only happens for Sitebuilder 2.x)
This error is thrown out because file /usr/local/sitebuilder/include/config.php is really absent.
In turn if this file is absent it most probably means that...
I had the same problem, in my case the reply from qmail during attempts to send mail was:
And the same errors in the maillog:
It can be easily fixed by removing the invalid line, but - I'm not sure what caused this invalid line to appear in users.conf in the first place
license key is usually in /etc/psa/ but there is no need to backup it - upgrade does not delete it, the worst thing it can do with license is automatically upgrade it from 8.x to 9.x license format.
that's what I was afraid of - you have Plesk main packages installed from three different branches:
as well as some other packages, but this one is the most important.
Usually it happens when upgrade fails in the middle of psa package upgrade - in such cases some files are upgraded to 9.2...
your log file says that the update has failed - and if you have a mix of Plesk packages for different versions then such error is not the worst thing that can happen :)
I recommend you to check what Plesk packages are currently installed:
# rpm -qa | grep psa-
And at first you should...