• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Restart Server doesn't work after update 18.0.33

Next step (after re-installing 18.0.33)
repair all
say:
errors occured while performing the following actions: plesk packages permissions.
plesk_18.0.33_repair_problems.log
doesn't exist

Question:
where are the plesk packages permissions located and how have I to change them?
 
@DieterWerner There are a lot of previous threads that include the same type of 'challenge', not sure if you've had time to search & then read through them all yet, but it may be worth it if you do. Quite often, their resolution includes the use of THIS and/or the GUI version; the Plesk 'Repair Kit' extention. Don't think there's sufficient detail in that last post, for anybody to provide a really useful answer for you yet.
 
All of this was nothing else but a bad joke of the Plesk panel.
Clicking 'Restart Server' let the server reboot immediately but did not close the panel page before.

Conclusion:
'Restart Server' works but the panel .... ?
 
OK - it has been installed but it didn't change anything.
So I'm going back to the drawing board
After having tried many unsuccessful methods yourself, surely, you can raise a support ticket now? (posts #13 #14 #15 #16 #17)
You can overcome your moral dilemma (posts #16 & #17) by having factually now proven that you've left this option until the very end.
You do want to solve this asap (as 18.0.34 will be along soon!) & you do have restorable backups to return to 18.0.32 if/when needed.
That ^ sounds like #TicketTime ;)
 
After having tried many unsuccessful methods yourself, surely, you can raise a support ticket now? (posts #13 #14 #15 #16 #17)
You can overcome your moral dilemma (posts #16 & #17) by having factually now proven that you've left this option until the very end.
You do want to solve this asap (as 18.0.34 will be along soon!) & you do have restorable backups to return to 18.0.32 if/when needed.
That ^ sounds like #TicketTime ;)
You wrote it very diplomatically.
What you want to say is:
don't get on our nerves any longer. ;)
 
Back
Top