Skip to main content
angie1996
New Member
December 18, 2020
Question

I have problems with this page work.workplace.com

  • December 18, 2020
  • 4 replies
  • 6192 views

Hello everyone, I have problems with this page work.workplace.com. When adding this link to a policy in the fortigate so that they can access, the page when loaded is shown as the image. What could be the problem? help me please

    4 replies

    Toshi_Esumi
    SuperUser
    SuperUser
    December 18, 2020

    Check the page's source code. All style sheets and a Javascript are at static.xx.fbcdn.net. You must be blocking access to the FB's static content server(s).

    deksar
    New Member
    April 7, 2021

    Hi,

    I've exactly the same problem here. And yes, it's due to "static.xx.fbcdn.net" is blocked. I tried adding as "allow" or "exempt" that url, as simple, also fbcdn.net as wildcard, nothing worked. It's still blocked. How can I allow static.xx.fbcdn.net fbcdn.net while blocking Facebook?

     

    Any idea much appreciated,

    Best.

    TuncayBAS
    Explorer
    April 7, 2021

    You should only allow static.xx.fbcdn.net as a urllist in your webfilter profile.

    deksar
    New Member
    April 7, 2021

    Thank you so much for your reply, Mr. Tuncay.

     

    However, I still have the same problem, getting a bad/corrupted website, just like the attached image on workplace.com.

     

    Just as you said, I removed everything in URL filter list, and added static.xx.fbcdn.net as Simple and Allow. The list works good on my clients, (both allow and block URLs), it's just this subdomain doesn't work. 

     

    Best regards.

    Santhiago
    New Member
    May 14, 2024

    Hi,

    I've exactly the same problem.  I've inserted "static.xx.fbcdn.net" and "work.workplace.com" addresses in "Exempt from SSL Inspection" on ssl/ssh certificate.

    sw2090
    SuperUser
    SuperUser
    May 15, 2024

    Screenshot looks very typical for page unable to load its stylesheet(s). Even if you exempted them from SSL Inspection make sure that not your web- or dns-filter does block it.