• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Upgrade from 7.5.2 -> 7.5.4 & my domains are down

C

cYon

Guest
The update said it was succesfull, however, now I can't access any of domains via http/https. One thing I did notice in the update log was the following:
Trying to start BIND server... done

BIND server starts Ok.


Now BIND server shutting down...

Trying to stop BIND server... ***** upgrade minor problem report *****
stop BIND server
named service failed to stop
----------------------------------------------

I'm also getting lots of errors when testing DNS over at: http://www.dnsreport.com/tools/dnsre...webreports.com

I'm at a loss on what to do! Please let me know if you need any other info! TIA!

Aug 31 00:02:17 u15177724 named[2155]: starting BIND 9.2.3 -u named -c /etc/named.conf -u named -t /var/named/run-root
Aug 31 00:02:17 u15177724 named[2155]: using 1 CPU
Aug 31 00:02:17 u15177724 named[2155]: loading configuration from '/etc/named.conf'
Aug 31 00:02:17 u15177724 named[2155]: /etc/named.conf:397: zone '255.160.217.in-addr.arpa': already exists
Aug 31 00:02:17 u15177724 named[2155]: loading configuration: failure
Aug 31 00:02:17 u15177724 named[2155]: exiting (due to fatal error)
Aug 31 00:02:17 u15177724 named: named startup succeeded
 
Problem seems to be resolved. I commented out the suspect entry and named started right up!
 
Back
Top