• This warning or error has been going on for months. I figured someone else would be getting it and notify you. Maybe it’s just my site then? I’m not interested in sharing my website address publicly here so if you want to know what it is you’ll have to contact me directly, just let me know in your response. This warning or error shows up on every single page/post that accessibility is enabled on, basically, it shows up sitewide.

    Warning: file_get_contents(https://www.mydomain.com/website-management-care-plan-is-fundamental-to-website-success/?c=1625071600): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /home/customer/www/mydomain.com/public_html/wp-content/plugins/accessibility-checker/includes/simplehtmldom/simple_html_dom.php on line 84

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Amber Hinds

    (@alh0319)

    Hi @benjino,

    Thank you for submitting a support ticket. This is the first we have heard of this error.

    If you want to privately email us your domain so we can take a look, you may email it to us. It would help us if you sent a full copy of your System Info, which can be found at /wp-admin/admin.php?page=accessibility_checker_settings&tab=system_info

    Is this a front-end or backend error?

    Thanks!

    • This reply was modified 2 months, 3 weeks ago by Amber Hinds. Reason: Removed email address since email has been sent
    Plugin Author Equalize Digital

    (@equalizedigital)

    Hi Benjamin,

    We wanted to provide you with a quick update just to reassure you that our development team is aware of the issue and is working towards a solution.

    If we have any additional questions, we will follow up. In the interim, we will leave this open as an unresolved issue.

    Thank you!

    Plugin Author Steve Jones

    (@stevejonesdev)

    @benjino, Is the website you’re running the plugin on password protected?

    Thanks!

    Thread Starter benjammin

    (@benjino)

    No, it is not on a password protected directory.

    Plugin Author Steve Jones

    (@stevejonesdev)

    @benjino, We’re having trouble duplicating the warning on our end. The warning is returning the ‘forbidden’ status code. This could be caused by the server preventing access to the file or it’s limiting requests. You could contact the server administrator to see if any permissions or limits are set on the directory. Also, another conflict might be with the iThemes Security Pro plugin. You could try disabling that plugin to see if the warning goes away.

    Please let us know if you’re able to resolve the issue by either of these means.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.