Unable to access instance's editor in Safari

[ppawlowski]

Current Behavior

After creating a Node-RED v4 instance, I cannot access the editor using the Safari browser. Instead, unauthorised error is presented. Please take a look at the attached video (the video presents the accessing editor for the instances running on different NR versions as well).

https://github.com/user-attachments/assets/daa549d2-7fe7-4157-a5f4-6ac2bb07e6b8

Expected Behavior

I should be able to access Node-RED instance using Safari browser.

Steps To Reproduce

1. Create an instance with Node-RED version 4.0.2
2. Once it becomes ready, try accessing the editor using the Open Editor button

Environment

• FlowFuse version: FlowFuse Cloud
• Node.js version: n/a
• npm version: n/a
• Platform/OS: n/a
• Browser: Safari (17.6 (19618.3.11.11.5))

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[joepavitt]

This may not be solvable, but needs to be investigated

[hardillb]

We have had customer raise this via support last night

[hardillb]

I was going to have a quick look at this, but as there isn't a windows build of Safari any more, I can't even run it in a VM or on my windows machine.

[Steve-Mcl]

Would a sensible MVP be to detect browser is safari and simply open the editor in non-immersive mode (like it used to)?

[ppawlowski]

I'm not sure if anything has been done in this area, but I no longer experience the described error.

Safari version: 18.5 (20621.2.5.11.8) macOS version: 15.5 (24F74) Node-RED Version: 4.0.8 Launcher Version: 2.13.1-37cb723-202501161010.0

[ppawlowski]

After another review it turns out, that the problem exists on FFC production environment only. The following error has been observed in the browser's console while accessing the editor:

Blocked a frame with origin "https://app.flowfuse.com" from accessing a frame with origin "https://pp-headers-test.flowfuse.cloud". Protocols, domains, and ports must match.