Has anyone else encountered this? We just upgraded our HTML5 receiver from 19.1 to 1908 and now when users try to connect in a browser with uBlock they are getting a white screen and the desktop doesn't load. It looks like there is a call-back to googletagmanager.com which gets blocked.
Is this call meant to be in the client or has it been left in this build accidentally. I'd really rather not have to ask our users to disable their ad-blockers to use an internal service.
Question
FRASER ROBERTSON
Has anyone else encountered this? We just upgraded our HTML5 receiver from 19.1 to 1908 and now when users try to connect in a browser with uBlock they are getting a white screen and the desktop doesn't load. It looks like there is a call-back to googletagmanager.com which gets blocked.
Is this call meant to be in the client or has it been left in this build accidentally. I'd really rather not have to ask our users to disable their ad-blockers to use an internal service.
Link to comment
19 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now