Hello,
I have a very strange issue.
About three days ago I updated my Plesk to Obsidian from Onyx and my Debian 8 to 9. Everything ran fine.
The server was up and running, the domains were working. I also had to get a new key from my reseller as my old one still was one from the old licensing system. But installing the new Web Pro Edition Key also worked fine.
Ab bit later, I am not sure how long exactly, but it was always in the evening for the next 3 days in a row, the server acted strangely. I couldn't reach any of the domains and after I logged into Plesk I got the message "The license key is invalid" This alone would let me turn to my provider how gave me the key, but the page also reloaded the whole time, like every second. So I was unable to put in the key again or any new one.
I then decided to go the SSH route an did a plesk repair. This solved the issue. Domains were back online, key was valid again, I could log in to Plesk. About 24 hours later the same game again. And now for the third time. It worked an hour ago or maybe two, so it definitely worked for 19-20 hours this time, not sure for the other two days.
Anybody an idea, how to fix that? I am so glad it is only a backup server with some private domains on it, but I need to update my client-server, too, and I am now a bit freaked out. The client-server already has a new key from the new licensing model, it is working fine there. But this server is still Onyx with Debian 8.
P.S: I forgot, before I could login via SSH I had to reboot the server ones over my provider's rescue system as even SSH was failing "The SSH session has terminated with error. Reason: FlowSocketReader: Error receiving bytes. Windows error 10054: Eine vorhandene Verbindung wurde vom Remotehost geschlossen." After the reboot the plesk login still had the invalid key and constant reload error, but SSH was working again. The domains also worked again after the server reboot.
I have a very strange issue.
About three days ago I updated my Plesk to Obsidian from Onyx and my Debian 8 to 9. Everything ran fine.
The server was up and running, the domains were working. I also had to get a new key from my reseller as my old one still was one from the old licensing system. But installing the new Web Pro Edition Key also worked fine.
Ab bit later, I am not sure how long exactly, but it was always in the evening for the next 3 days in a row, the server acted strangely. I couldn't reach any of the domains and after I logged into Plesk I got the message "The license key is invalid" This alone would let me turn to my provider how gave me the key, but the page also reloaded the whole time, like every second. So I was unable to put in the key again or any new one.
I then decided to go the SSH route an did a plesk repair. This solved the issue. Domains were back online, key was valid again, I could log in to Plesk. About 24 hours later the same game again. And now for the third time. It worked an hour ago or maybe two, so it definitely worked for 19-20 hours this time, not sure for the other two days.
Anybody an idea, how to fix that? I am so glad it is only a backup server with some private domains on it, but I need to update my client-server, too, and I am now a bit freaked out. The client-server already has a new key from the new licensing model, it is working fine there. But this server is still Onyx with Debian 8.
P.S: I forgot, before I could login via SSH I had to reboot the server ones over my provider's rescue system as even SSH was failing "The SSH session has terminated with error. Reason: FlowSocketReader: Error receiving bytes. Windows error 10054: Eine vorhandene Verbindung wurde vom Remotehost geschlossen." After the reboot the plesk login still had the invalid key and constant reload error, but SSH was working again. The domains also worked again after the server reboot.
Last edited: