Closed fervi closed 5 years ago
I have not tested using TOR. I will need to investigate what may be causing this.
Do you get the same error on https://www.zapread.com (Using SSL) and http://www.zapread.com?
The error itself occurs on the normal Internet, then only through the TOR you can enter, because other browsers also prevent from logging in.
However, the error solves itself after a few hours, so if I will have it again, then I report.
I have the same problem.
I am having a hard time finding the cause. I get it if I skip the www part on Zapread.
I think it may be a web server configuration. Still searching for a solution.
Very odd bug.
If I am running zapread.com in default Chrome profile, a error is show.
But.
If I am running zapread.com in private mode Chrome then website is a good working.
I noticed that bug showed when I runnin zapread.com in profile browser which I use on a daily basis and I'm logged in to my profile in zapread.com
Summary
Browser | Logged in to the profile in zapread | Error |
---|---|---|
Google Chrome default mode | Yes | Yes, website is not working |
Google Chrome private mode | No | No, website is working |
Firefox default mode | No | No, website is working |
Google Chrome for Android default mode | No | No, website is working |
I am now logged in Firefox browser and website good working.
Screenshots
Ok, I think I solved it. I cleared cookies and cache in chrome, and then the problem stopped:
I think this could be something from a configuration change I made on the website. Note that now all requests go directly to SSL (https).
Anyway, I think this is the only fix. And I think only early users from before my configuration change are affected. I still don't understand the cause.
I found the cause!
It's my hosting provider, which provides an application firewall called Site Guard.
"Error detected by Application Firewall 1 QUICK START (Must Read) This is usual application firewall thing which is introduced for data security.
In case above error appears on your website, you can login to hosting control panel > security > site guard > turn ON and then OFF Site Guard from there, it will fix this issue."
So I did this and hopefully this doesn't happen anymore.
Good job! I am observing behavior a website. Do not close the bug yet.
Closing this one - It looks like it's fixed.
I suppose the bugged script blocks users (me too) from accessing the site to an IP address. You need to use TOR to use Zapread. Sometimes it's fixed, but it's not supposed to work ;)