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.
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.
/etc/init.d/httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs!
Just reboot your machine. I would say just manually kill any leftover apache processes, but given you are not familiar with the commandline, I suggest rebooting the box instead. It should fix the issue.
Hi.
I recently had the same issue and a reboot fixed it.
Could someone please shed some light on what the message means? What may be causing it...and what can be done to prevent it in the future?
Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs!
Did a find, but nothing showed up, could you tell me what may be wrong with plesk/apache since it's not there?
httpd component also shows as not installed.
The issue stems from the fact that apache hangs in a 'running' state, so a graceful start/restart won't work because apache is already bound to the socket. Doing a forceful stop/start (restart) will unbind apache from the port and re-bind it.