• 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.

Resolved Watchdog says Plesk Web Server down since 18.0.79

K

King555

Silver Pleskian
Server operating system version
Ubuntu 24.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.79 Web Admin Edition
I just upgraded Plesk to version 18.0.79 and now the Watchdog extension says that the Plesk Web Server service is down, which is obviously not the case, because I can access Plesk.

I guess it has something to do with with my custom Plesk port. After the upgrade the two config files with the ports were overwritten and had the default ports. Now I set them back to my custom port and restarted Plesk. But before the upgrade I also had the custom port and disabled the default ports in the config files. What changed?
 
Here are the last 50 lines of that file:

Code: 
[2026-06-29T08:44:21+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:46:21+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:46:21+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:46:21+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:46:21+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:48:21+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:48:21+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:48:21+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:48:22+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:50:22+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:50:22+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:50:22+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:50:22+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:52:23+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:52:23+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:52:23+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:52:23+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:54:23+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:54:23+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:54:23+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:54:23+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:56:24+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:56:24+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:56:24+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:56:24+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T08:58:24+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T08:58:24+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T08:58:24+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T08:58:24+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:00:25+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T09:00:25+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T09:00:25+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T09:00:25+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:02:25+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T09:02:25+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T09:02:25+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T09:02:26+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:04:26+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T09:04:26+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T09:04:26+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T09:04:26+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:06:26+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T09:06:26+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T09:06:26+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T09:06:27+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:08:27+0200] error    : 'plesk_apache' failed protocol test [generic] at [localhost]:8443 [TCP/IP TLS] -- Connection refused
[2026-06-29T09:08:27+0200] info     : 'plesk_apache' trying to restart
[2026-06-29T09:08:27+0200] info     : 'plesk_apache' stop: '/bin/systemctl stop sw-cp-server.service'
[2026-06-29T09:08:27+0200] info     : 'plesk_apache' start: '/bin/systemctl start sw-cp-server.service'
[2026-06-29T09:10:28+0200] error    : 'plesk_apache' service restarted 1000 times within 1000 cycles(s) - unmonitor
 
After seeing the log entries I added listen 127.0.0.1:8443 ssl default_server; to /etc/sw-cp-server/conf.d/plesk.conf (the file still includes the line listen 127.0.0.1:8880 default_server;). And this time I did not only run service sw-cp-server restart, but also service sw-engine restart.

It seems that these two things solved my issue.
 
You must log in or register to reply here.

Similar threads

H.W.B
Issue Watchdog down after Plesk update
Replies
7
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
websavers
Resolved Enabling server wide smarthost via CLI does not show in UI
Replies
3
Views
2K
websavers
websavers
Steve Jeffery
Resolved "Import Dump" from file on server fails since update to 18.0.79
Replies
11
Views
5K
AmaZili Communication
AmaZili Communication
Bitpalast
Question After update to 18.0.79 AWStats is still present, but change log says it was removed
Replies
14
Views
10K
learning_curve
learning_curve
K
Issue Emails that are sent locally inside the server are rejected – PPPM-7190 not fixed with 18.0.79
Replies
9
Views
4K
King555
K
Back
Top