Webpage not loading proplerly

[Tarun1]

Hi All,

Currently we are having an issue where, when users browse to https://www.concursolutions.com/nui/signin or https://www.concursolutions.com, the website does not load properly and sign-ins fail. Browsing to the same when not on our network (mobile hotspot or home internet) the page loads and work properly.Also, if I set the policy for a client to whitelist ((Clients > Policy > Device Policy > Allow List)) the page again loads and works correctly. I have tried adding the domain to Content Filtering > Allowed URL list without any luck.

Browser network logs are showing that scripts are being blocked when the page is trying load.

Any suggestions on how to allow or whitelist this domain?

Cheers

[aleabrahao]

What version are you running? You can request a site category change.

Do you see any blocks in the logs?

Also take a look at this.

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering#Using_the_Catch-All_Wildcard_(*)_in_URLs

[Tarun1]

Hey, We are running version 17.10.6. Did try the suggestions listed in the link you shared without much luck.

[aleabrahao]

Check it out.

https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering/Content_Filtering_Troubleshooting#Troubleshooting_Content_Filtering

[Philip D'Ath]

My guess is not that page directly, but content from another site referenced by that page is blocked.

I used Chrome developer tools, and this is the domains that are used:

Try whitelisting those - or running them through the content filter lookup tool to see which URL is being blocked.

[Tarun1]

Hey, None of the domains in your screenshot are being blocked. When I inspected the page in Chrome I am see that the CSS and JS files hosted on concursolutions.com have a "failed" status. Not sure how to "allow" these.

[Philip D'Ath]

You can add this domain to the whitelist.

The other possibility is they are blocking you ...

[Tarun1 · Accepted solution]

Firstly, thank you both for trying to help.

Ended up finding that the issue was due a Layer 7 firewall rule we use. Had to tweak this rule.