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.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
Additionally, the plugin update initially failed, yet it appears to be updated and no further updates are available. Is it safe to uninstall and reinstall the plugin?
It also seems that my other Plesk server with an identical setup is experiencing the same issue.
Hello,
I have updated Plesk to version 18.0.75 and upgraded the Microsoft Azure DNS module to the latest release. Since then, DNS changes are no longer synchronizing. When attempting to access the application settings, the following error is displayed.
Anyone have any idea?
Kind Regards...
I have a same or similar problem.
Hundreds of customers their MX records are not being send to Azure, all the other records do.
Ofcourse all of them losing their MX record and not being able to mail is a very big problem.
Hello,
Right now we have the external SMTP server setup via smtp.office365.com and basic auth.
Since this is retiring in september this year, are there any plans of adding Oauth 2.0 to this feature?
Kind Regards,
Quinten
Hello, please look into the following and also DMARC record:
SPF
The SPF record for your domain should include all email senders for your domain. If your third-party senders aren't included in your SPF record, messages from these senders are more likely to be marked as spam.
DKIM
Important...
This is my current setup:
The red being a public ip4 and the blue being local 10., could this be the issue?
This is a vm hosted on Azure.
Many thanks on trying to help!
I am sure yes, also tried running the cron from a different plesk server with the following result:
Task " https://www.example.be/nl/module/gsitemap/cron?token=exampleid&id_shop=1" completed with error in 0 seconds, output:
curl: (3) URL using bad/illegal format or missing URL
Unable to fetch...
I have seen this thread and tried the suggestions , nothing seems to work
i updated to the newest plesk .61 hoping it would fix things or have an effect.
no result sadly, i dont know much specifics about cron jobs commands but I have changed the command to:
curl -l -k...