Has anyone else experienced this? Could it be a global outage affecting the Forge tunnel ↔ Cloudflare integration? Any thoughts on how to resolve this?
Everything was working fine yesterday across multiple apps, but today, all of the apps that use the resolver via the bridge are facing the same issue.
It appears to me that the Custom UI part of my part was successfully tunnelled to my dev server while the resolver backend was not. Thus it doesn’t seem to be a total outage but only the Forge FaaS is unable to tunnel.
You are definitely not the only one, I am running into this myself this morning.
A work around is to run a deploy for any API side changes, and iterate on the client side using the tunnel, but it is certainly making iterations on the API side more challenging.
I have every confidence this thread will be seen by the right people, when their timezone comes on-line. However, I would recommend reporting a clear problem like this with developer support. That formal channels is the best way to make sure tickets get logged and action will be taken as quickly as possible.
@KaiserSoft and others,
I attempted to reproduce the issue but was unsuccessful. I have contacted Cloudflare to inquire about any potential outages. Is this error still persisting?
@LashaniPerera,
I’ve tested it with several apps, and everything is now working as expected. There are no more error messages from Cloudflare. Thank you!
