Once or twice a week, for the last six months, my Website gets blocked by a message reading:

403 Forbidden
openresty/1.19.9.

I am not doing any programming at the time this message appears, much less dabbling with permissions.

The message appears out of nowhere. It appears on two different computers in my house, both on Firefox and Chrome. There is no error message on my phone however.

Both my ISP and hosting provider say they can load my site without a problem. They never see the OpenResty error message.

It seems like the only one blocked from seeing my site is myself, the site owner.

Despite repeated calls, the ISP and hosting provider say it's not their problem.

The host, Network Solutions, says they will look further into it, but only if I pay them $70 for their "MyTime" service.

Can someone please tell me what might be going on here?

It seems to me it's either an error with OpenResty (about which I admittedly know nothing at all) or an error with my router or modem.

But the ISP seems to think that the router and modem are not at fault.

Thanks for any ideas on how to fix this irritating issue. The error message usually appears for a half-hour and then disappears by itself -- but today it has been blocking me from my site for over an hour and counting.

*I reset permissions on my shared hosting site to default, that didn't help.

    And today I'm blocked with a new error message:

    Secure Connection Failed

    An error occurred during a connection to www.quass.com. Peer reports it experienced an internal error.

    Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

    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.

    bquass28 you can check the access log of the openresty to see if there are any logs of 403.
    If the request is proxy to upstream, you may need to check the log of the upstream.

      What access log and where, please? I have a shared hosting service with access logs. Is that where you mean?

      I would like to know whom to contact about this, however, since I am not causing the problem. I mean, I am never coding or changing my website when these error messages appear. It must be something wrong with the modem, router, my ISP or my host.

      Just getting the error message again, "Forbidden," once again blocking me from accessing my own site. I tried accessing the site using my host's numeric address for the site rather than my domain name, but that does not work either.

      I really need to find someone who can tell me why OpenResty keeps shutting me down so I can do no work.

        The log files is in /usr/local/openresty/nginx/logs by default.
        I don't know if you have changed the log directory.

        8 days later

        The logs show file not found errors, nothing to indicate why I'm blocked from my own site.

          4 days later

          I've posted my question in the mailing group.

            2 years later

            zhuizhuhaomeng

            Hi. I'm still being blocked intermittently by openresty and my hosting people insist it's not their problem. However I do not have access to the usr directory, except daily access and error logs, which make no reference to openresty. It seems to me it must be an issue with my web host. If I knew that for sure, I could hassle them until they give me an answer.

              Hi. I'm still being blocked intermittently by openresty and my hosting people insist it's not their problem. However I do not have access to the usr directory, except daily access and error logs, which make no reference to openresty. It seems to me it must be an issue with my web host. If I knew that for sure, I could hassle them until they give me an answer.

                Hi. I'm still being blocked intermittently by openresty and my hosting people insist it's not their problem. However I do not have access to the usr directory, except daily access and error logs, which make no reference to openresty. It seems to me it must be an issue with my web host. If I knew that for sure, I could hassle them until they give me an answer.

                  Write a Reply...