Applicable to:
- Plesk for Linux
- Plesk for Windows
Symptoms
After moving a Sitejet published website to new server, Sitejet no longer opens the existing website but instead creates a new one with the option to choose a template.
Cause
Sitejet assigned a new website ID on the new Plesk installation, and it's not connecting to the correct Sitejet website in the cloud.
Resolution
Update the Sitejet website ID in the Plesk database to match the existing site.
- Open the affected website in a web browser
- Press Ctrl + U on the keyboard to view the source code
- Search for "
webcard.id" to find the website ID (e.g. 111111) - Log in to the Plesk server over SSH
Backup the Plesk database:
# plesk db dump psa > sitejet_backup.sql
Update the Sitejet website ID on the database:
Note: replace
<sitejet_website_id>with the one from step 3, andexample.comwith the affected domain# plesk db -e "REPLACE INTO dom_param (dom_id, param, val) SELECT id as dom_id, 'ext-plesk-sitejet-website_id' as param, <sitejet_website_id> as val FROM domains WHERE name ='example.com'"
Comments
Please sign in to leave a comment.