• Resolved Manuel5cc

    (@manuel5cc)


    I have temporarily disabled w3 total cache to make some adjustments and now the site is showing a 403 error for visitors. I have tried turning caches off first one by one and purging but it doesn0t fix it. What I could figure out is that the error might be related with browser cache but not the reason.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @manuel5cc

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Disabling W3 Total Cache should not cause a 403 error. However, there might be some issues with the leftover files or rules in nginx/apache.
    Can you please share the website URL?
    Also please check your nginx.conf/.htaccess a remove any W3TC rules and check if possibly have any other rules that may be in conflict?
    Thanks!

    Thread Starter Manuel5cc

    (@manuel5cc)

    Hey there!
    I had also deleted the w3tc rules from .htaccess with the same result. The website url is https://www.manuel5cc.es/

    Thanks!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @manuel5cc

    Thank you for the information.
    Yes I see the `Forbidden
    You don’t have permission to access this resource.`
    This error can be triggered due to incorrect file/folder permissions on the webroot directory. If the default file permissions are not adjusted to grant users access to the website files, then the chances of this error popping on a web browser are high so please check the permissions.

    $ sudo chmod -R 775 /path/to/webroot/directory

    Also, you should check directives in Apache main configuration file It could be an incorrect parameter that has been included or missing directives in the configuration file.
    Your hosting provider should be able to assist you with this more.
    Thansk!

    Thread Starter Manuel5cc

    (@manuel5cc)

    I found out that was a duplicity error.
    I had two “Options” directives that conflicted when the cache was disabled. I don’t know why “configtest” was not detecting this issue.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @manuel5cc

    Thank you for the information.
    Glad to know the issue is resolved.
    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘403 error after disabling’ is closed to new replies.