Zero Trust Too Many Redirects When Try to Join Organization

What is the name of the domain?

fiylex.cloudaccess

Related to

I don’t know / other

What is the error number?

ERR_TOO_MANY_REDIRECTS

What is the error message?

ERR_TOO_MANY_REDIRECTS

What is the issue you’re encountering

. Now, I can’t access either my previous organization or any new one.

What steps have you taken to resolve the issue?

Hello. I had joined my organization through the Cloudflare Warp app with Zero Trust, but I accidentally left the organization through the Warp app. Now, I can’t access either my previous organization or any new one. When I enter fiylex.cloudflareaccess.com, I get a “too_many_redirects” error. I’m using Windows 10.

I’m using Zero trust for self-hosted application.

I cannot reproduce the same while accessing your team domain in my Web browser.

May I ask if you’ve tried clearing your Web browser cache, cookies & data?
How about using an Incognito Mode (private window)?
Have you tried using a different Web browser to access?

Are you still the member or Super Administrator of the team? If not, could you contact someone to add you back to it?

Hello, I tried using a different web browser, incognito mode and cleaning browser cache,cookie and data. Still I’m the Super Administrator of the team. But I’m still getting this error.

I created a new organization with a new account. I configured like the other organization but Still I’m getting err_too_many_redirects.

Could you try to access the URL and do this through the Zero Trust Dashboard using the link https://one.dash.cloudflare.com/ instead of using the Warp app? :thinking:

Wonder if it’s something with the Warp app then.

Wonder does the error happen after you successfully logged-in using OTP and pass the Access screen, or how? :thinking:

Meaning, something with self-hosted app is broken, possibly using Flexible under SSL/TLS tab for your app/zone at Cloudflare dashboard?

Furthermore, please try change application Cookie Same Site Attribute from “Strict” to “Lax” instead if you’re having such settings configured.

Without seeing the actual paths and process involved, as far as it’s behind Access, it’s difficult to troubleshoot. Temporarly remove the URL from the Access so we can test and provide you with more feedback how to proceed further.

How about this solution to try out if it would help you? :thinking: