• 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

Recent content by andreas.scherer

  1. andreas.scherer

    Issue Cannot activate monitoring

    Thanks for this valuable tip, I might have blacklisted the address with Imunify360. :oops:
  2. andreas.scherer

    Resolved Plesk Monitoring = An unexpected error occurred

    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...
  3. andreas.scherer

    Resolved Plesk Monitoring = An unexpected error occurred

    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. ;)
  4. andreas.scherer

    Issue Cannot activate monitoring

    The system is only 7 days old and is completely up to date. Monitoring with Plesk 360 also worked for about 2 days. suddenly it didn't work anymore.
  5. andreas.scherer

    Issue Cannot activate monitoring

    I'm using Plesk Obsidian 18.0.49, in Centos 7 I used: [root@www conf]# yum update ca-certificates Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached host file * base: de.mirrors.clouvider.net * epel: mirror.23m.com * Extras: ftp.plusline.net * updates...
  6. andreas.scherer

    Resolved Plesk Monitoring = An unexpected error occurred

    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?
  7. andreas.scherer

    Question Misconfiguration of certificate's CN and virtual name ...

    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?
  8. andreas.scherer

    Question Misconfiguration of certificate's CN and virtual name ...

    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...
  9. andreas.scherer

    Issue Problems with installing memcached for PHP 8.2

    Is the file there on the right place? Did you assign the correct permissions to that file?
  10. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (8443)

    IP-Adressen IP-Adressen anzeigen, hinzufügen und entfernen IP-Adresse hinzufügenIP neu lesenEntfernen 2 Elemente insgesamtEinträge pro Seite: 10 25 100 Alle IP-Adresse Öffentliche IP-Adresse Schnittstelle IP-Typ Websites 172.17.145.125 /255.255.0.0 xxx.xxx.xxx.xxx eno1 gemeinsam...
  11. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (8443)

    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...
  12. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (8443)

    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...
  13. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (8443)

    No, the templates are as it where installed. If nginx is enabled nginx should catch all traffic and send it to apache or the plesk-engine. IMHO
  14. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (8443)

    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...
  15. andreas.scherer

    Issue Apache and sw-cp-server uses the same ports (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! ;)
Back
Top