Plesk | Web publishing problem

Helpdesk Plesk
1

Hi everyone, I’m having a publishing problem and I don’t know how to solve it.
We redesigned a website in Plesk with a temporary domain, but when we try to publish, it takes us back to the option to add a new domain.
This has never happened before.

I cloned the website (within the same subscription) and the same thing happens.
I tried cloning it to a new Plesk subscription outside of the previous one, but it didn’t work either.

Has anyone else experienced this? Any ideas on how to fix it?
Thanks!

2

Upon reviewing the data, the last website I published was on March 17, 2026. I logged in, changed some text to republish it, and this behavior is still occurring. It’s not just on new domains but also on websites that were previously published.
I’ve restarted Plesk and checked for SiteJet updates, but without success.

3

Since March 17, 2026, the publishing feature has completely broken on a server-wide level. It affects both newly created domains and existing older projects (even if I just try to publish a 1-letter text change).

The Symptoms: When clicking “Publish” inside the Sitejet editor, the process fails silently. Instead of publishing, the Plesk iframe breaks and redirects me to the default Plesk “Add New Domain” screen.

Troubleshooting already done:

  1. Server Logs: The /var/log/plesk/panel.log is completely clean. There are no 500 Internal Server errors, and no webhook/API exceptions registered. The request never seems to hit the Plesk core properly.

  2. SSL/DNS: Checked and discarded. The domains have valid certificates.

  3. Browser Console (The culprit): Inspecting the Network tab during the publish attempt shows the following request being rejected with a 302 Found redirect:

GET /modules/plesk-sitejet/index.php/publish/run?site_id=[ID]&csrfToken=[TOKEN] Status: 302 Found

My Questions for Support/Devs:

  1. Was there a silent patch to the Plesk extension or the Sitejet API around March 17 that could be causing this 302 redirect on the /publish/run endpoint?

  2. Support usually suggests running plesk bin extension --uninstall sitejet to fix corrupted environments. Given that I have 150 active projects mapped in my Plesk database, is this command 100% safe? Will I lose the relational database mapping between the Plesk domains and the Sitejet site_ids, or will it reconnect automatically upon reinstallation?

I cannot risk losing the relational mapping of years of work. I need a non-destructive way to restore the extension’s routing.

You can check the ID “2932586“, “2883996“ is one of new websites i need to publish, this is old “2915115“ but i can update something.

Thank you.

4

Hey Carlos,

I think you need to address this issue to the Plesk support directly. But please keep us updated here :pray: