Cannot access G@G from my internet, tried multiple browsers and devices with no luck. Connected to different internet I have no problem?

[llorando]

This is the message I get in firefox.

Secure Connection Failed

An error occurred during a connection to www.girlsaskguys.com.

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

Updates

+1 y

In chrome I get ERR_HTTP2_PROTOCOL_ERROR

Updates

1 y

Should have updated question long ago, but anyways, turns out a weird bug with my cable modem was causing the issue. Issue went away after doing a factory reset of my cable modem.

[SoMuchNut]

There's only one internet. What do you mean by a different internet?

[llorando]

Different internet connection.

[sawno]

Sounds like a web filter interfering, its likely blocked.

[llorando]

I have no web filter.

[sawno]

What happens if you deliberately visit http://www.girlsaskguys.com ?
Because a HTTPS protocol error happens when your experiencing issues with the security protocol of the website which commonly happens because of either configuration issues (But would be limited to one device) or filters on the internet provider or network. If you specifically type http:// in front of the domain you will force your system to use http and you might be able to get an indicator why its not working on the usual secure connection,

[llorando]

I typed in http:// I got a error message (below). Currently the only way I'm able to access G@G on my own internet connection, is through Opera browser with VPN enabled. Strangely I'm able to access G@G when connected to Xfinity wifi.

This site can’t be reachedThe webpage at https://www.girlsaskguys.com/ might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR

[llorando]

Should have updated dated long ago, but anyways, it turns out it was a strange glitch that developed in my cable modem. One day I had to do a factory reset on my cable modem (unrelated to this issue), and after the factory reset the issue was gone.