Common Sitejet Issues and Solutions
Issue: Sitejet Builder Not Visible
Symptoms: No Sitejet option when adding domains, or missing from "Get Started" tab
Solutions:
- Verify your hosting plan has "Access to Sitejet Builder" permission
- Contact hosting provider to enable the permission
- Update Sitejet extension to version 1.3.1 or higher
- Refresh Plesk components: Tools & Settings → Server Components → Refresh
Issue: API Key Problems
Symptoms: Sitejet asking for API key, or "Sitejet API Key" prompt appears
Solutions:
- Go to Extensions → Sitejet → Manage Licenses
- Deactivate and reactivate the license for your domain
- If that fails, reinstall Sitejet via Tools & Settings → Updates → Add/Remove Components
Issue: Publishing Stuck at 60%
Solutions:
- Clear browser cache and try again
- Check server disk space
- Verify network connectivity
- Check Plesk event logs for errors
- Contact support with your Plesk license key
Issue: Images Not Displaying
Solutions:
- Check domain error logs for PHP errors
- Verify PHP is enabled for the domain
- Re-publish the website
- Clear CDN/browser cache
- Check image file names for special characters
Issue: "Cannot Access Sitejet Website Builder" Error
Symptoms: Error when trying to edit existing Sitejet site, often after migration
Solutions:
- Find website ID in page source code (look for webcard.id)
- Note your domain name
- Have your Plesk license key ready
- Contact Plesk support with this information
Issue: Permission Errors During Publish
Symptoms: "filemng: Error occurred" or "You dont have permission" messages
Solutions:
- Check file/folder permissions on document root
- Verify .well-known directory permissions
- Clear any file locks
- Contact hosting support for permission reset
Note: Sitejet is a non-officially supported product. For complex issues, Plesk support may be required.
Important Disclaimer: Sitejet Builder is a third-party product provided by Plesk, our control panel vendor. Adaptive Web Hosting does not formally support Sitejet. Support for Sitejet-specific issues should be directed to Plesk.