content was blocked because it was not signed by a valid security certificate

[dafroeh]

Since last Thursday (1/30/2020) when I try and edit my site I get the following error message "content was blocked because it was not signed by a valid security certificate" and I cannot load the site editor, it sits there doing nothing. I've tried using Microsoft Edge (Windows 10), Google Chrome, 2 different computers and 2 different internet providers. Something changed on your site. I downloaded the app on my iphone and tried to edit the site but it screwed the format up on the site. Any help you could provide would be appreciated. I believe it has something to do with your site and not on my end.            https://etbbl.weebly.com/                                                                                                                                               

[bjs1]

Same problem here. . . Hello Weebly??

[acdotp123]

Also having the same issue.  I contacted customer support and was told it was most likely my school's firewall; however, my IT director checked and everything was all set on his end.  He added the IP ranges that customer support told us to add and it made no changes.  

[ChewbaccaDad]

Having the same problem with my weebly website.

[socalinsured]

same problem day three

[m_cichelli]

Same problem with two completely independent Weebly sites - but ONLY at my office.  I can run the editor perfectly from home. They say, "We've heard reports that some major service providers who are used by a large number of school, office, and privately-managed networks as well as VPNs have blocked certain network resources that allow some programs to run."  They threw the problem back at me and my IT guy.  Anyone found anything else out about this.

[Bernadette3]

Was your IT guy able to add the IP range to accepted sites? From what I've been told, there is not much we can do from our end although I'm sure it is actively being looked into. 

[darbyrand]

I'm having the same problem. I've tried to edit on explorer and chrome and it just pops up with this same block.

[Bernadette3]

Hi there. Are you using a work or school network? Do you have a separate internet connection you can test, like mobile data? 

[TEVest]

Same issue for me.  Trying to access through home network for editing.  Tried Chrome and IE.  Neither work to load the site editor

[Bernadette3]

This is the information that was provided to us from customer support: 

“We’ve heard reports that some major service providers who are used by a large number of school, office, and privately-managed networks as well as VPNs have blocked certain network resources that allow some programs to run. In particular, problems seem to arise surrounding a resource named “Umbrella Roaming Client”, though your network provider would be responsible for determining exactly which resources are being blocked. There are three options to remedy the situation:

First, you can reach out to the person who manages your network firewall (and/or your IT department) and ask them to add Weebly to the software’s “safe” or “accepted” list. You can let them know that our IP ranges are 199.34.228.0/22 and 74.115.48.0/22

Second, you can use a different internet connection altogether and ensure that you are not using any kind of VPN service.

Third, you or your IT team can reach out to any VPN providers you are using to help locate and unblock any blocked resources. If you are on a privately-managed network and are experiencing problems loading your site editor, your best option is reaching out to your Internet Service Provider to report the error, and providing them with the same two IP ranges listed above.

While we’d love to provide more specific instructions, this error is being caused by a change made by major network and internet infrastructure providers and is not something that Weebly has any control over or ability to fix ourselves. We understand this is frustrating, with the instructions above whoever manages your network may be able to quickly resolve the issue.”

There is another user on here that did say that disabling the "umbrella roaming client" fixed the issue for him. I'm honestly not 100% on what that is though, so I would definitely recommend doing your research first.