Forge tunnel on macOS Sequoia doesn’t seem to work

Forge Forge Rookies
1

Hello everyone,

I’ve recently started exploring Forge and tried to use forge tunnel on my Mac mini (M4) with macOS Sequoia. It doesn’t seem to work but there is no error message shown in the Terminal or in the browser console. The only symptom is that when refreshing the Confluence page (I’m using Confluence macro module with UIKit) the part with the macro is not loaded and the “wheel” to indicate loading of data keeps on spinning. When I quit the tunnel, the macro gets loaded. So I am able to deploy and upgrade changes, but this is not efficient :wink:

What I’ve already tried or checked:

  • checked the node-version (18.12.0)
  • checked the system log for errors
  • disabled my firewall (both on the Mac and router)
  • read through the documentation and searched a lot - there just seem to exist problems with the “old” tunnel

Any help is appreciated!

Best regards
Julia

2

Hi Julia,

It think there is a bug with NodeJS 18 where it defaults to IPv6 instead of IPv4, which can cause problems connecting to localhost.
I would recommend trying out NodeJS 20 and see if it sorts things out for you

3

Hey,
thank you very much for your answer! I’ve tried using NodeJS 20, but it doesn’t seem to make a difference.
But I’ve noticed an entry in the browser console:

[Warning] [blocked] The page at {…} requested insecure content from http://localhost:8000/. This content was blocked and must… {here it ends}

4

Hi @JuliaAckermann,
May I know which browser you are using. It is supported in Chrome and Firefox browsers. I assume you are using the latest version of @forge/cli version as well.

5

Please excuse my late reply and what I have to admit - I’ve read the docs and understand it was just using CustomUI that is supported in specific browsers only. I’ve used Safari before but tried Chrome now - of course the tunnel is working now…
So, sorry for being stupid!

6

No worries, I’m glad it worked