Your website is currently password protected

Hi @kespinoza,

Your site is not password protected but you have a username and password set in the Accessibility Checker settings. Can you remove those credentials, save the settings and then update a page/post so it will scan again?

Let me know if that fixes the issue.

Thanks,

Steve

Thanks for the quick response.

I don’t see a username and password option under the Accessibility Checker settings.

My apologies. Those setting are now only available in the Pro plugin.

If you go to this page on your site.
https://staging.ufcw135.com/wp-admin/options.php

You can remove the username and password from these fields:

edac_authorization_password
edac_authorization_username

Screenshot:

https://capture.dropbox.com/0KNbGO7GrPo3KGMA

Once you’ve removed those fields scroll to the bottom and click Save Changes.

• This reply was modified 1 year, 7 months ago by Steve Jones.

This is the URL: https://staging.ufcw135.com/wp-admin/options.php

I removed the user name and password but I’m getting the same result “your website is currently password protected”.

Did you update a post/page so the plugin can rescan?

I did and cleared the cache.

I’m still getting the message “It looks like your website is currently password protected.” I have updated a page, cloned a page, and created a new page. I can’t seem to resolve this issue. Any other thoughts?

Hi @kespinoza,

I’m thinking that the server might be blocking the plugin from scanning. Can you contact your hosting company and confirm that the allow_url_fopen is set to true in your php.ini file. I know this is a bit technical that’s why I suggest contacting your host support.

Thanks for the reply.

allow_url_fopen is set to On. But I am still getting the password protected message.

It may be an SSL issue on your local. You can bypass the SSL validation by adding this filter to your functions.php file. For security reasons, it’s not recommended to do this on a live website.

add_filter( 'edac_no_verify_ssl', '__return_true' );

The filter didn’t resolve the issue. I installed the plug-in on a demo site that is on a different server than the staging site I’m working with and it works fine. This must be something server specific that is causing the issue. I’ll contact the web host and see if thy have any thoughts.

We’ve released an update (version 1.3.24) that might help with this issue. If after updating you still can’t scan please let us know.

Thanks!

Hi

Just a follow up on this one.

This issue has been bothering me for a while. We use this plugin on our not-for-profit multisite, and the “passworded” message and the plugin not running/checking has been on-going for a while now. I have kept the plugin installed on 1.3.20, as it seemed to be the last one that worked fine.

I finally got around to asking our hosting dev if he could check it out.

After his intervention the plugin is now running/checking fine with no messages. I thought I would share his findings.


“Basically the plugin is doing http requests on it’s own rather than using the native WP api, and when doing so it’s overriding the request options, which in turn overrides our defaults options which include our proxy settings.”

He added the following at line 201 in accessibility-checker/includes/validate.php




$default_context_opts = array(
// See: https://www.php.net/manual/en/context.http.php.
‘http’ => array(
‘user_agent’ => ‘PHP Accessibility Checker’,
‘follow_location’ => false,
‘proxy’ => ‘tcp://proxy.**********.net:****’,
‘request_fulluri’ => true,
‘verify_peer’ => false,
‘verify_peer_name’ => false,
‘header’ => [“Proxy-Authorization: Basic “.base64_en
code(“****************************.net:”)]
),
“ssl” => array(
“verify_peer” => false,
“verify_peer_name” => false
)
);




Obviously, on plugin updates these changes will be lost and I’ll need to add them back in again, but I thought you may be interested in the code.

Kind Regards

Thanks for the post. I added the code with my proxy information, but it still didn’t work. The reading level works, but all other details are 0. I haven’t contacted the host yet, but will this week and follow up if I learn anything new.