New Discourse business CDNs are blocked by Websense/Forcepoint

Forum CDN assets (CSS/JS) requested from newly registed domain are being blocked by Forcepoint’s Websense Content Gateway. As such, I see a blank page as no CSS or JS are being loaded.

A newly registered domain seems to be one registered within the past three months.

Examples of assets blocked:

Basically everything.

This seems like something that should be reported to websense, not us?


iBoss is blocking you too, they think you distribute maiware. And while I could report it to iBoss and say they are wrong, it seems like an online reputation issue Dicourse would want to correct.

I have never heard of iboss, if they have bad data that reflects poorly on them, whoever they are.

1 Like

Thanks for the reply?? I’m just trying to get our users able to view a community site served up on your product. If two filtering system and blocking, that means something and I have gone back to the vendor asking them to review the classification. Like the OP, seems to not like the js and undefined reference errors. . . declare before calling. Or bash me for posting an issue, whichever.

If you’ve chosen a filter which throws up false-positives and prevents your users from using another of your services, how exactly does that become the fault of the team?

Do people contact Microsoft when an installation of Exchange is unable to relay email to an organisation which implemented crude spam heuristics? iBoss is a commercial product, if you’re paying them for support surely that’s a part of the contract?

1 Like

I suggest contacting them and letting them know they are mis-classifying the URL for our CDN. If there is anything we can change on our end let us know.

1 Like

I work for one of their competitors, they should have a mechanism for you to request a manual review. Same with the original post, a lock down on new URLs isn’t unusual, especially really new ones. If they don’t have a review request mechanism I’m happy to introduce you to one of our sales teams :slight_smile:


I’m going to assume that contacting the companies in question to correct the misclassifications corrected the problem.

1 Like