Hey all, sorry about the issues you are having.
Just to provide a short history of what has occurred. Ngrok disabled anonymous access, and as a temporary workaround, we informed the community to use --ngrok-config. However, this isn’t the greatest experience for developers to enter the config path every time they tunnel, which is why we’ve now replaced the option with a setting. This was announced in the changelog and it had to be a major version change for the CLI, but we haven’t considered what will it look like for people who bravely upgrade and try the command again - it should have prompted you to set the setting as well. Thanks for providing this feedback.
We are currently researching alternative options to the current tunnelling solution, with the ultimate goal of delivering a frictionless experience. We will post more details on this when we are ready to announce our plans.
Regarding the issue you are facing, we do have tests regarding tunnelling on both old and new runtimes. I just tried myself and it’s working for me. Could you please check if you have any ngrok processes hanging around, as that might cause the new one to reject the connection; if that doesn’t help post the ngrok output of forge tunnel --verbose.