I can't access the site on my main browser.

[ownedbycats]

Main browser is Vivaldi 7.4.3684.43. A modified Chromium essentially. Get ERR_HTTP2_PROTOCOL_ERROR. Also clean profile, can't be put down to extensions.

Site works on Waterfox, which is based on Firefox.

[JSWolf]

Originally Posted by ownedbycats

Main browser is Vivaldi 7.4.3684.43. A modified Chromium essentially. Get ERR_HTTP2_PROTOCOL_ERROR. Also clean profile, can't be put down to extensions.

Site works on Waterfox, which is based on Firefox.

It's working with Edge which is also based on Chromium.

[PeterT]

See https://forum.vivaldi.net/topic/9874...ers-all-work/2 for some ideas

[ownedbycats]

Sadly, I not have access to MR's server settings.

[Comfy.n]

Yes, I checked got the same error on Vivaldi. Not my main browser. WF FTW

[Desertway]

A couple of days ago I became unable to view the site on any browser on any device on my network. I haven't had the same issue on any other website. I can still access it using 4G on my phone.

[PeterT]

I can't help but think that there is an NGINX gateway fronting a cluster of two (or more) machines hosting MobileRead and that the issues are at that gateway.

[SteveEisenberg]

Here's how the problem appears to me:

For the last two days or so, I have been unable to get to mobileread using Verizon Fios WiFi. I have tried disabling OpenDNS, changing the browser, using the IP address, and powering down all devices in the house that have gone to mobileread.com except for the PC or tablet I am testing. On Chrome, the consistent message is "www.mobileread.com took too long to respond." I just downloaded waterfox and the message is "The connection has timed out" regardless of whether I put in the IP4 address or www. mobileread.com.

No other web sites seem to have the problem, and I do not recall these symptoms in the past.

Here is what I get with nslookup from my Windows 11 PC:

C:\Users\MyUserName>nslookup 162.55.243.172
Server: CR1000A.mynetworksettings.com
Address: 192.168.1.1

Name: www.mobileread.com
Address: 162.55.243.1

HOWEVER, I have no problem when using my Motorola Android phone on the Verizon cell network.

[JSWolf]

Originally Posted by SteveEisenberg

Here's how the problem appears to me:

For the last two days or so, I have been unable to get to mobileread using Verizon Fios WiFi. I have tried disabling OpenDNS, changing the browser, using the IP address, and powering down all devices in the house that have gone to mobileread.com except for the PC or tablet I am testing. On Chrome, the consistent message is "www.mobileread.com took too long to respond." I just downloaded waterfox and the message is "The connection has timed out" regardless of whether I put in the IP4 address or www. mobileread.com.

No other web sites seem to have the problem, and I do not recall these symptoms in the past.

Here is what I get with nslookup from my Windows 11 PC:

C:\Users\MyUserName>nslookup 162.55.243.172
Server: CR1000A.mynetworksettings.com
Address: 192.168.1.1

Name: www.mobileread.com
Address: 162.55.243.1

HOWEVER, I have no problem when using my Motorola Android phone on the Verizon cell network.

Try connecting with Edge and see how you get on.

[DiapDealer]

Originally Posted by JSWolf

Try connecting with Edge and see how you get on.

It's pointless for people who don't use Edge to see if it will work with Edge.

There's something bigger than browser brands going on here. When wifi doesn't work, but 5G or LTE does, it ain't the name of your browser that's the problem.

[SteveEisenberg]

Re last two posts, I did retest with Edge. Message says "took too long to respond."

P.S. ping gives "request timed out" four times for both the IP4 address and www.mobileread.com. So I'd say both the browser and DNS are not the issue.

[ownedbycats]

Originally Posted by SteveEisenberg

Re last two posts, I did retest with Edge. Message says "took too long to respond."

P.S. ping gives "request timed out" four times for both the IP4 address and www.mobileread.com. So I'd say both the browser and DNS are not the issue.

open command prompt and tracert mobileread.com. I get a timeout after a Hetzner server.

[ownedbycats]

It's not a DNS issue if the domain resolves to the IP, btw.

[pdurrant]

I have heard from Alex that there has been a DDOS attack on MobileRead over the past few days, which has caused slowdowns. Blocking a DDOS requires blacklisting IP addresses. Alex told me that over 2 million IPs have had to be blocked.

It's possible that some blacklisted addresses are also used by some MobileRead members, thanks to IPs using dynamic IP allocation. If you (say) access MobileRead from your mobile data connection, but not from your cable modem connection, this might have happened to you.

I would hope things will get back to normal soon.

[issybird]

I’m struggling. My free Proton VPN stopped connecting to MR just now; I switched to Tunnel Bear on a different device, but there’s a data limit on that.