Issue CRITICAL: Sitejet Extension /publish/run returning 302 Redirect

[Benti]

Server operating system version

Debian 12.13

Plesk version and microupdate number

Plesk Obsidian 18.0.75, actualización 1 Web Host Edition

Hello Plesk community/support,

I am experiencing a server-wide failure with the Plesk Sitejet extension. Since March 17, 2026, the publishing routing has completely broken. This affects over 150 active Sitejet projects on my server (both newly created domains and older ones trying to update).

Important Context:I have already escalated this to official Sitejet Support (Plesk | Web publishing problem) . After reviewing the behavior, they explicitly redirected me to Plesk support, confirming that their API is functioning correctly and the 302 redirect is being generated locally by the Plesk extension's routing (index.php), not by them.

The Issue:When a user clicks "Publish" inside the Sitejet iframe, the action is aborted, and Plesk forcefully redirects the user to the default "Add New Domain" screen. The website is never updated.

Technical Details & Logs:

1. /var/log/plesk/panel.log is completely clean. No 500 errors, no fatal exceptions from the extension.
2. SSL/TLS certificates and DNS are perfectly valid.
3. Inspecting the browser's Network tab reveals the exact point of failure. The GET request to the extension's controller is being rejected with a 302 Found:

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

My Questions for Plesk Engineers:

1. Why is the extension's controller suddenly rejecting valid site_ids and tokens with a 302 redirect to the domain creation page? Was there a silent update to the extension around March 17 that broke the routing?
2. Standard support often recommends running plesk bin extension --uninstall sitejet followed by a reinstall. Given that I have 150+ domains currently mapped in the psa database to their respective Sitejet projects, is this command strictly safe? >I cannot risk wiping the relational mapping in the psa database and permanently disconnecting my clients' local Plesk domains from their cloud Sitejet projects. I need a non-destructive command to fix the extension's broken endpoint.

Thank you.

 

[Sebahat.hadzhi]

Hi, @Benti . Could you please enable Plesk debug mode, then replicate the issue and double-check if there are any new entries logged into /var/log/plesk/panel.log? Thank you in advance.