Forge tunnel problem

I can’t execute “forge tunnel” and it says as below.
What should I do?

1 Like

Do you have Docker installed and running? Docker getting started

Or you could try the Node.JS runtime that doesn’t require Docker

1 Like

I installed Docker and I think I’m running it.
Just in case, could you tell me how to run Docker?

When I run “forge tunnel”, it says Error: Failed to start tunnel, could not establish a connection.
Could you tell me how to improve this?

Now you need a ngrok account (mandatory for connection).
You should use the native mode (Node.JS runtime) to avoid using Docker.

A few checks that can be useful:

echo $FORGE_EMAIL should return your email address…
also check echo $FORGE_API_TOKEN
If not, authentication must be set in .zshrc (or whatever file launched when you open a session): FORGE_API_TOKEN et FORGE_EMAIL

You need a ngrok account (for tunneling), and get a authtoken: ngrok - Online in One Line

Check if ngrok-config-path is already set in forge:

forge settings list

If not, do it this way:
forge settings set ngrok-config-path "[path to your ngrok config file. something like /Users/YOU/Library/Application Support/ngrok/ngrok.yml]"

I hope this will help.

1 Like

Is the ngrok-config-path OK?

echo $FORGE_EMAIL and echo $FORGE_API_TOKEN return nothing.
What should I do?

Thanks to you, I have made some progress, but it still says as below.
Is there any possible cause for this?

It looks like it’s working!
That warning message tells you that main.js is fairly large, which can be slow in a browser.
If you’re using big libraries in your frontend code (e.g. image editors, WYSIWYG…) that’s probably the cause. You can tinker with your webpack config to split the bundle in multiple chunks, switch to Vite which is generally a bit more optimized, or just ignore it: it’s probably going to be fine when developing. If your app becomes big and famous, you’ll want to take care of it then :smile:

1 Like

Is it no problem that checking Docker image is failed?

I can’t run Docker as shown below.
It says The manifest.yml file is not a valid YAML. Fix it and try again.
I also show the content of manifest.yml.

Could you help me?

Ooof my bad, I read your message before my coffee and misunderstood :smile:
One thing that I can suggest you is using the new runtime that doesn’t require Docker: in my experience it’s much faster

OK. I will try it.

@hirokinishimaki An issue I’ve noticed in the manifest.yml is the resource path. It should point to the build folder rather than the source location. By default, it should be set to static/hello-world/build, but you may need to adjust it according to your project’s structure.