Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
Ok, here we are:
Output from "# cat panel.log | grep "Unable to Connect to ssl" | less
---
[2023-01-29 21:39:12.104] 822:63d6e78019633 ERR [extension/monitoring] Http client exception: Unable to Connect to ssl://api.monitoring360.io:443. Error #0:
[2023-01-29 21:49:11.509] 4133:63d6e9d77c30e ERR...
Miracles happen! I was just about to search the logs and suddenly the monitoring works as it should. The question is how long it lasts. But I'll try to find the relevant log sections anyway. But I think, that takes a while. ;)
I have the same problem with Plesk Obsidian 18.0.49 on Centos 7.0.2009
When I click on Monitoring, a white screen appears after a few seconds with the message "An unexpected error occurred" and then nothing happens.
Even a '# plesk repair install' doesn't help.
Anyone an Idea?
I have already run the #plesk repair web and #plesk repair all command line commands, but without first deleting and reinstalling the certificate. I will do that now. Thanks for the tip!
How can I change the login for the administrator. The login url?
Hi all out there!
My new Plesk installation is getting on my last nerves! I changed the server domain. Running the "hostname" command in the shell also gives me the correct hostname. However, the old host name is still in the SSL certificate. Have already renewed the certificate 3 times. Always...
Very interresing for me is that on my 2nd server apache behaves correct.
[root@lingua ~]# netstat -tulpen | grep 8443
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 0 26452 1198/sw-cp-server:
tcp6 0 0 :::8443 :::* LISTEN 0 26453...
Let's giv us a try!
[root@andreas ~]# plesk repair web
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates ......................... [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for...
Unfortunately, Obsidian only lasted 3 hours. Now it has the same problem again.
Why does sw-cp-server occupy the ipv6 port 8443?
The httpd listens on this port.
As far as I understand nginx is listening on port 80 and 443.
The sw-cp-server should be listening on the ipv4 address port 8443...
Hi All!
After I made the correct DNS setting for all domains, I was able to start everything clean with the original configuration.
Sorry for the "unnecessary" traffic here. Maybe an admin can delete the issue thread here.
Is just a suggestion! ;)
OMG the changed version must look like this one. :)
server_names_hash_bucket_size 64;
server {
#listen 8443 ssl;
listen 8880;
listen 127.0.0.1:8880 default_server;
include conf.d/*ipv6_ports.inc;
ssl_certificate /usr/local/psa/admin/conf/httpsd.pem;
ssl_certificate_key...
Hi All!
I think I have a solution for the described problem:
I changed /etc/sw-cp-server/conf.d/plesk.conf
from
server_names_hash_bucket_size 64;
server {
listen 8443 ssl;
listen 8880;
listen 127.0.0.1:8880 default_server;
include conf.d/*ipv6_ports.inc...
Hello dear specialists and others! ;)
Since 3 days I'm trying to get things fixed.
Like mentioned in the headline my problem is that either sw-cp-server is running on port 8443 and plesk-interface works or I kill sw-cp-server and - bingo - apache service is starting and running. They simply...