• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Resolved How to Fix Sitejet Access Error on Plesk Without Migrating the Website?

it_tks

New Pleskian
Server operating system version
Red Hat Enterprise Linux 9.4 (Plow)
Plesk version and microupdate number
Plesk Obsidian 18.0.65 Update #2
The issue I encountered is that after not accessing Sitejet for some time, I attempted to modify the website and encountered the error shown in the attached image. I did not migrate the website or make any changes. I would like to know if there is a solution to this issue. I have another server running Plesk, and it does not have this problem—this issue is specific to this server.

1734946329738.png



I tried testing by creating a new domain and website, but it showed this error.
1734946549333.png
 
Hello, @it_tks. Could you please provide me with the following details in a private conversation? If you don't have the option to open one, please let me know and I will do so:

  1. Website ID - Open the domain and search for webcard.id in the source code. You should find a number with at least 6 digits.
  2. Domain name
  3. Plesk license key
 
Hello, @it_tks. Could you please provide me with the following details in a private conversation? If you don't have the option to open one, please let me know and I will do so:

  1. Website ID - Open the domain and search for webcard.id in the source code. You should find a number with at least 6 digits.
  2. Domain name
  3. Plesk license key
Thank you for your assistance.
 
Hello, @it_tks. Could you please provide me with the following details in a private conversation? If you don't have the option to open one, please let me know and I will do so:

  1. Website ID - Open the domain and search for webcard.id in the source code. You should find a number with at least 6 digits.
  2. Domain name
  3. Plesk license key
Hello
i've a same problem.
can you help me too?
 
Ladies and Gentlemen

we have a Plesk server. This Plesk server (hosting6.headroom.at) runs as a VM in our VMware infrastructure. Among other things, hosting is set up on this server that uses the Sitejet Builder extension.

I had to upgrade the operating system of this server (from Debian 10 to 11). In order to be able to test the OS upgrade in advance, I duplicated (cloned) this virtual Plesk server, assigned a new IP address and imported a Plesk test license.

The cloned test server is now offline again.

However, we now have the following problem on the “real” Plesk server (hosting6.headroom.at.

A website hosted on the Plesk server was created using the Sitejet Builder extension. However, since our cloned test server was online, this website can no longer be managed via the Sitejet Builder extension: the following error message appears:

Error: Cannot access Sitejet Website Builder for this domain. Please check whether this domain has been migrated to another server or restored.

Is there a possibility that taking my test vm online changed anything in the API key from this SiteJet installation?

Can you help me get a working API key again?

Best regards
Matthias Gaede
 
Back
Top