# SiteJet starts onboarding while site already exists (Help)

**URL:** <https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826>\
**Category:** Plesk\
**Created:** [July 24, 2026, 8:35am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826 "2026-07-24T08:35:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc\_Eren](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@Marc\_Eren](https://community.sitejet.io/u/Marc_Eren)\
**Post date:** [July 24, 2026, 8:35am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/1 "2026-07-24T08:35:33Z")

</div>

Hello Community and Team,

one of our customers wanted to continue working on an existing SiteJet website hosted in Plesk. Plesk seems to recognize that a SiteJet project exists, as the **SiteJet Builder** section currently displays the message **“Website not published yet”** , which suggests that a website was created and saved, but never published.

However, when we click **SiteJet Builder** , SiteJet starts the onboarding process and asks whether we want to create a new website using AI or a template. Neither option is appropriate, since the website already existed and should simply be editable.

Has anyone experienced this before or knows what could be causing this?  
Do you need the SiteJet project ID or any other information to investigate?

![grafik](https://europe1.discourse-cdn.com/flex017/uploads/sitejet/original/2X/6/6de7945c10f4a52ee617e6a1bef6c92e98158edf.png)

---

<div class="post-metadata">

**Author:** ![Kalisperakichris](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/kalisperakichris/32/3572_2.png) [@Kalisperakichris](https://community.sitejet.io/u/Kalisperakichris)\
**Post date:** [July 25, 2026, 11:22am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/2 "2026-07-25T11:22:26Z")

</div>

Have you checked with your hosting provider?

If the website files still exist on the server (similar to how cPanel works), your hosting provider may be able to restore or reconnect the Sitejet project, depending on how it was originally created.

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [July 27, 2026, 7:32am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/3 "2026-07-27T07:32:46Z")

</div>

This. And if they can not, your provider contacts Plesk and reconnect the correct website. It is important that this gets escalated towards Plesk so they can check why this happens and fix it.

---

<div class="post-metadata">

**Author:** ![Marc\_Eren](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@Marc\_Eren](https://community.sitejet.io/u/Marc_Eren)\
**Post date:** [July 29, 2026, 7:54am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/4 "2026-07-29T07:54:21Z")

</div>

Thank you very much- for some reason it now works again.  
This can be closed.

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [July 29, 2026, 10:17am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/5 "2026-07-29T10:17:31Z")

</div>

Hey Marc,

I can see in the internal platform that the website has been reconnected to your server 🙂

---

<div class="post-metadata">

**Author:** ![Andre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.sitejet.io/andre/32/3459_2.png) [@Andre](https://community.sitejet.io/u/Andre)\
**Post date:** [July 29, 2026, 10:17am UTC](https://community.sitejet.io/t/sitejet-starts-onboarding-while-site-already-exists-help/5826/6 "2026-07-29T10:17:38Z")

</div>