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.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
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! ;)