Forge tunnel can't connect with ngrok

I’m retaking the development of an app made in Forge after two to three weeks of not touching it, at that time Forge tunnel was working without any issues, but now that I’m trying to get back to it, it just doesn’t work anymore and I have no idea why. I tried building the app again, re-deploying, re-installing everything, etc. The app is working without issues when running forge deploy, but I need the tunnel to be able to debug the event triggers.

forge --version: 6.16.2
docker --version: Docker version 23.0.5, build bc4487a
running on: WSL Ubuntu 20.04.6 LTS

Here is the forge tunnel --verbose output:

forge tunnel --verbose

Forge tunnel -

Note: can’t post the logs because it won’t allow more than 2 links

docker output
INFO[2023-09-04T11:43:37.055189747-03:00] Pull session cancelled
ERRO[2023-09-04T11:43:37.487452321-03:00] Not continuing with pull after error: error creating lease: context canceled
time="2023-09-04T11:43:38.986188702-03:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2023-09-04T11:43:38.986250521-03:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-09-04T11:43:38.986260741-03:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2023-09-04T11:43:38.986512250-03:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/34748a04b2c4934fb220c529c534c010328e126cbdd07a9aba4123ba9bb97efc pid=6932 runtime=io.containerd.runc.v2
INFO[2023-09-04T11:44:00.812710325-03:00] shim disconnected                             id=34748a04b2c4934fb220c529c534c010328e126cbdd07a9aba4123ba9bb97efc
WARN[2023-09-04T11:44:00.812767145-03:00] cleaning up after shim disconnected           id=34748a04b2c4934fb220c529c534c010328e126cbdd07a9aba4123ba9bb97efc namespace=moby
INFO[2023-09-04T11:44:00.812797045-03:00] cleaning up dead shim
INFO[2023-09-04T11:44:00.812815374-03:00] ignoring event                                container=34748a04b2c4934fb220c529c534c010328e126cbdd07a9aba4123ba9bb97efc module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
WARN[2023-09-04T11:44:00.818476058-03:00] cleanup warnings time="2023-09-04T11:44:00-03:00" level=info msg="starting signal loop" namespace=moby pid=7095 runtime=io.containerd.runc.v2

Hi @RicardoCsped,

I haven’t been able to reproduce the issue.

If you’re still experiencing this problem, could you be experiencing a network issue? could there be a firewall blocking the port?
The next step might be to test on a different network if that option is available to you.

I don’t think it is a network issue because I can make a tunnel with standalone ngrok for other apps in the same ports, I also checked ports with my ISP and with firewall disabled, besides, it was working fine a couple of weeks ago without any change to any kind of settings. I also tested in my phone’s shared data network (the only other network I have available) with the same results, and it’s also working fine for some other colleagues.
I don’t know what else to try and the logs don’t say much about the issue, is there another way to set up or configure the tunnel?