Recent content by Ruben

I solved it. Most of the solutions suggested above have to do with certificates for specific domains. These certificates all worked fine on my server, and repairing, restarting apache, restarting nginx etc. didn't do anything to the one used by Plesk. For me it was only this certificate that...

I ran the SQL query, only Let's Encrypt certificates showed up. I also went through the certificates directory but there are no references to the Thawte certificate there either. I also did 'plesk repair web -sslcerts' for both the domain.com and server.domain.com as the article suggested. All...

I did re-check the IP setting. With only one certificate available in my server pool there is no point in re-allocating. On SSL Checker: same result. On port 443 for instance "We have not detected any issues." (correct certificate) and on port 8443 "expired 4 days ago" (Thawte).

I have specifically created a server.domain.com certificate, from the SSL/TLS Certificates page. It's not a wildcard certificate (tried this first but not any more). I have no other certificates left in the server pool, only this Let's Encrypt certificate. When I access domain.com I get a...

Made it the default certificate. Still no change, Chrome keeps warning me about the expired Thawte. I may have found another clue: when I go to domain.com, I get a certified HTTPS connection. However when I go to domain.com:8443 there is this warning. How is that even possible?

I had a Let's Encrypt wildcard certificate for domain.com so I guessed my Plesk under server.domain.com would also be covered? Anyway I have now registered a new Let's Encrypt certificate directly from the SSL/TLS Certificates page. It is visible in the server pool and set to secure the Plesk...

The default is the 'plesk' certificate which I believe is self-signed. Isn't this only used for newly created domains? It says it is in use for 1 domain. There is also an incomplete 'default certificate' in use for 9 domains. However the Thawte certificate is nowhere to be found, I deleted it...

Two years ago I bought an SSL certificate from Thawte, which I used to secure my Plesk installation on server.domain.com. Now that the two years are over, I got a message in my browser that Plesk is not longer secure, so I wanted to replace it with a common Let's Encrypt certificate. I removed...

I have the same issue... Latest Plesk Obsidian and CentOS.

Thanks Monty. Good to know you can do "plesk repair mail" even for one specific address. That seems to have solved it. It still surprises me that I don't have the horde database but let's not worry about that now.

I recently tried to rename an e-mail address. While it seems the address was indeed renamed, Plesk threw me an error: "Table 'horde.imp_sentmail' doesn't exist" which seems to be related to this: Unable to access Horde webmail or rename a domain in Plesk: Table 'horde.table_name' doesn't exist...

Probably the Plesk server sw-cp-server is not running. Kill all related processes and try to start it manually via SSH and see from there.

Looks like you made my day, mate. I had already searched myself but somehow that didn't come up. Solved the issue though, many thanks.

Thanks Tom. I'm not sure this applies to my server though, I don't see any of the configuration files mentioned there. I did this: [root@server ~]# netstat -tulpn | grep 8443 tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 8976/sw-cp-server tcp 0...

I've just upgraded to Obisidian. The process seemed to go well, but in the end I couldn't log into Plesk. When I go to my server address :8443, I get redirected to https://www....be:8443/login_up.php?success_redirect_url=https://www.....be:8443/ but that's an empty screen. All I'm seeing is a...