Username:
TITLE
Webmail Broken After Update to 18.0.61.5
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian Web Pro Edition
Version 18.0.61 Update #5
PROBLEM DESCRIPTION
Our users use Webmail extensively, so we know that it was working up into last night. This morning at 07:02 hours, Plesk shows, "Update version: 18.0.60.1 -> 18.0.61.5"
Now, the webmail.domain.com page shows the Apache "Testing 123" page. On opened/cached tabs, if you can get to the Inbox, the preview pane shows a Forbidden and an error regarding no permission to the skins folder, even though you can browse there manually with a web browser.
STEPS TO REPRODUCE
Navigate to webmail.domain.com and try to login.
ACTUAL RESULT
Unable to access webmail.
EXPECTED RESULT
Please provide a workout, patch, update, or way to rollback to the previous version.
Also, please advice as to the safest update settings to protect against such issues in the future until updates are known stable.
ANY ADDITIONAL INFORMATION
Thank you in advance. We have been using Plesk for around 20 years and it has been a God send. This is the first real issue we have had that has been "Plesk" related and just want to get all of our users back up ASAP.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out
TITLE
Webmail Broken After Update to 18.0.61.5
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian Web Pro Edition
Version 18.0.61 Update #5
PROBLEM DESCRIPTION
Our users use Webmail extensively, so we know that it was working up into last night. This morning at 07:02 hours, Plesk shows, "Update version: 18.0.60.1 -> 18.0.61.5"
Now, the webmail.domain.com page shows the Apache "Testing 123" page. On opened/cached tabs, if you can get to the Inbox, the preview pane shows a Forbidden and an error regarding no permission to the skins folder, even though you can browse there manually with a web browser.
STEPS TO REPRODUCE
Navigate to webmail.domain.com and try to login.
ACTUAL RESULT
Unable to access webmail.
EXPECTED RESULT
Please provide a workout, patch, update, or way to rollback to the previous version.
Also, please advice as to the safest update settings to protect against such issues in the future until updates are known stable.
ANY ADDITIONAL INFORMATION
Thank you in advance. We have been using Plesk for around 20 years and it has been a God send. This is the first real issue we have had that has been "Plesk" related and just want to get all of our users back up ASAP.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out