• 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 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?
 
Back
Top