• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Suddenly occurring error messages (Domain ID undefined and Invalid URL requested)

X1X11X

New Pleskian
Hi community!

Since a few days I get in the Plesk panel the errors that you see in the attached pictures, but I have no idea what causes these errors, I have already run the plesk-repair command and also updated to the latest version, unfortunately that does not solve these errors. The configuration of the server has not changed recently.

Maybe someone of you knows more about this, and can give me some help how to solve the problem.


Thanks!
 

Attachments

  • Screenshot_3.png
    Screenshot_3.png
    2.4 KB · Views: 8
  • Screenshot_4.png
    Screenshot_4.png
    2.7 KB · Views: 7
What is your Plesk version? Is it Plesk for Windows or for Linux?
Do you have enough free disk space there?
 
Have you tried to repair Plesk database with

plesk repair db

?
 
I have tried the repair command, it fixed showed several errors with some tables.
The result was that the console output said that everything has been fixed.

Although the above errors appeared again
 
Here's a quick update on the current situation:
I have tried the following things in the meantime:
- a manual update
- the repair command
- an update via the Plesk UI


Unfortunately, the error is still not fixed.
Also in the event log under the section "Plesk" nothing is logged.
 
I'd suggest you contact Plesk Support Team in this case.
 
I would like to give a brief update on the current situation here.
The problem no longer occurs, apparently it was not a specific Plesk problem but rather a configuration problem on the Windows server, after a reinstallation of the OS everything is now running smoothly again.
 
Have you tried to repair Plesk database with

plesk repair db

?
Thank you for the suggestion as the repair identified a problem with a duplicate key corruption that I resolved by removing the mysql user and then ran the repair utility again and it was able to repair. Search now works great! Thank you!
 
Back
Top