Thanks for the reply.
L7 filtering is indeed enabled and necessary CA certs have been installed on end devices, but I believe the issue is different here.
Yes, I’m using the correct teams name (“connect”, in my case) and device enrollment policy is configured. We’ve been using this for quite some time now and now all of a sudden, we’re unable to deploy the rules configured as signing in to client(s) fail.
If you can check, a simple GET to:
http://connect.cloudflareaccess.com/warp fails with HTTP 500 error.
Here’s the error from the desktop client:
and both of them are incorrect - I do have entered a valid org (that I’ve rechecked from the dashboard, and there are device policies configured). As I’ve mentioned, this setup used to be working before this.
The client is unable to handle the 5xx error and shows this message, for some reason.
In end-user mobile devices, the page loads in a single tab view and shows the same HTTP error (browser displayed page).