Hi,
After upgrading Review addon from 0.2.1 to 0.3.0, every review session closes immediately with “Ops”. Downgrading back to 0.2.1 works perfectly with the same versions and representations.
Server logs show:
text
review-0-3-0.sync.client | Client in a review session (Sync disabled)
review-0-3-0.sync.client | Client left the review session
Session joins then immediately leaves. Same Sync disabled log appears on 0.2.1 but stays open there.
Environment:
- AYON Server:
1.14.3+202603101719
- Review 0.3.0 — fails
- Review 0.2.1 — works fine
- Same published versions with valid MP4 review representations tested on both
Steps to reproduce:
- Switch bundle to Review 0.3.0
- Right-click any version with a review representation → Create Review Session
- Session opens briefly → “Ops” → closes immediately
Is this a known issue with 0.3.0?
Update after further investigation:
I did a deeper analysis of the browser console logs and network traffic and found the root cause.
The issue is a fatal frontend React crash in 0.3.0:
Error: useGlobalContext must be used within a GlobalProvider
This happens immediately after the WebSocket connects and the license check passes. The GlobalProvider (or equivalent) appears to be missing from the Review 0.3.0 component tree, causing the entire app to crash before rendering.
Additional findings:
License check for review: passing- License check for
powerpack: passing
- Backend GraphQL queries returning 200 OK with valid data
WebSocket warning: [review] Unknown WebSockets topic: {..., topic: joined} — possible protocol mismatch between server and 0.3.0 client- The
Client left the review session in server logs is a consequence of the frontend crash closing the WebSocket, not a backend issue
Environment:
- AYON Server:
1.14.3+202603101719
- Review 0.3.0 — crashes immediately
- Review 0.2.1 — works perfectly
This seems like a regression introduced in 0.3.0 where a dependency on a shared AYON frontend library (possibly @ynput/ayon-react-components) expects a provider that isn’t initialized in the 0.3.0 app tree. A fix in 0.3.1 would resolve it.
Hi, are you trying to access the review session through an unsecure http connection?
Thanks, that fixed it! Accessing via https://domain through nginx works perfectly.
One follow-up question — is there any way to make Review 0.3.0 work over plain HTTP? We’re on a local network and getting the “not secure” browser warning since we’re using a self-signed certificate. Is there a configuration option to allow ws:// instead of wss://, or is HTTPS strictly required for 0.3.0?
We’re currently experiencing issues with the new Reviewable plugin version 0.3.0 in the Chrome browser. Specifically, the review session crashes immediately after opening.
I attempted clearing the browser cache, but this did not resolve the issue. However, I noticed that switching the URL from HTTP to HTTPS prevents the crash. This leads me to believe the issue may be related to protocol handling.
Following this, I attempted to configure Ayon to run over HTTPS. I referred to the forum guide Ayon nginx setup configuration - #3 by BigRoy , and I do have a valid SSL certificate installed on the server along with updates to the nginx.conf file. Unfortunately, I haven’t been able to get this working successfully. Additionally, the Ayon Launcher does not seem to function when using HTTPS.
Could you please confirm:
Whether it is currently supported to run Ayon fully over HTTPS (including the Launcher)?
If so, is there any official documentation or step-by-step guide available for configuring HTTPS properly?
Are there any known limitations or additional steps required for local Reviewable workflows over HTTPS?
This is quite important for our team, as we rely on Reviewable for inhouse workflows and the cloud is not possible at that moment for the studio.
Can you try the latest server release? (assuming you’re not on 1.14.6 yet?)
production version of 1.14.6 is not released yet I guess! we facing the same issue with 1.14.5
hello, i am on the latest version of the server 1.14.3+202603101719.
yeah i saw your post we are facing the same problem for the launcher as it doesn’t open https, but from my search that we need to download the certificate put it in path enviro and i think ayon will trust it i don’t know really still trying.
1.14.5+202603301343
This is the latest server @Youssef_M_ElQadi , make sure you pull the latest image
2 Likes
okay thank you, but i think that won’t solve the main issue though