You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally, it shouldn't loop constantly (specially since their API will kick you with a HTTP 429), but I'm not sure on what is the best solution since I know that allowing redirects to open in the same container can leak data. Perhaps a way to manually assign a new site to a container without visiting it?
Additional informations
Manually visiting https://one.dash.cloudflare.com/ redirects you automatically to https://dash.cloudflare.com so you can login first.
Furthermore, limiting redirects does not seem to work for this (see this comment on #1670)
However, cutting off the internet does allow you to add the offending website https://one.dash.cloudflare.com/ as per this comment. This seems to be the easiest answer to this problem.
Also, as a bonus for folks that have pihole or adguard, you can set the offending website to the block list so that it doesn't resolve and it doesn't involve fully cutting off internet access on the computer running Firefox.
Provide a copy of Troubleshooting Information page (optional)
Perhaps a way to manually assign a new site to a container without visiting it?
Being able to actually edit the configuration would increase the UX of multi-account-containers a lot.
I often know which sites I want to open in which container, but I can't simply set it up. Instead, I need to visit each one and then click on things and then confirm that I really want to do what I just said I want to do.
It feels so unfinished with this basic interface, and issues like this one are difficult to fix because of it.
Before submitting a bug report
Step to reproduce
Actual behavior
The Zero Trust website is https://one.dash.cloudflare.com, which means it opens into the default container.
However, since https://one.dash.cloudflare.com requires you to login, it redirects you back to https://dash.cloudflare.com, which open in the container A. Then, as the https://dash.cloudflare.com knows you're logged in, it redirects you again to https://one.dash.cloudflare.com/ and the cycle repeats.
Expected behavior
Ideally, it shouldn't loop constantly (specially since their API will kick you with a HTTP 429), but I'm not sure on what is the best solution since I know that allowing redirects to open in the same container can leak data. Perhaps a way to manually assign a new site to a container without visiting it?
Additional informations
Manually visiting https://one.dash.cloudflare.com/ redirects you automatically to https://dash.cloudflare.com so you can login first.
Furthermore, limiting redirects does not seem to work for this (see this comment on #1670)
However, cutting off the internet does allow you to add the offending website https://one.dash.cloudflare.com/ as per this comment. This seems to be the easiest answer to this problem.
Also, as a bonus for folks that have pihole or adguard, you can set the offending website to the block list so that it doesn't resolve and it doesn't involve fully cutting off internet access on the computer running Firefox.
Provide a copy of Troubleshooting Information page (optional)
The text was updated successfully, but these errors were encountered: