Password protected site can’t be scanned

Hi @badro0

I hope you’re well today!

If you’re using “Cloud (new)” version of the scanner, it needs to be able to access the site and it can’t do it when site is password protected. It works just like crawlers do – crawling site’s pages from outside.

A “Local (old)” version Broken Link Checker engine should be able to work because it works “inside” the site: it hooks up to filters such as e.g. “the_content()” and similar to get page/post content directly from editor/DB instead of crawling front-end to find links.

Kind regards,
Adam

Hi Adam,

Thank you for the prompt feed-back !

Yes, that’s what I thought. But although I’m using the Local (old) version I’m getting this error. Any idea what could be causing this ?

Here is the detail of the response:

Link last checked: May 16, 2024
HTTP code: 401
Response time: 0.007 seconds
Final URL: https://example.com/messagerie/
Redirect count: 0
Instance count: 17
Log: === HTTP code : 401 === Response headers

HTTP/1.1 401 Unauthorized
Date: Thu, 16 May 2024 09:49:33 GMT
Server: Apache
WWW-Authenticate: Basic realm=”Protected ‘public_html'”
Connection: close
Content-Type: text/html; charset=iso-8859-1 Request headers

HEAD /messagerie/ HTTP/1.1
Host: example.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.34 Safari/537.36
Accept: /
Referer: https://example.com
Connection: close

Link is valid.

Hello @badro0,

If this link is from a different password-protected site, then that’s expected behavior. I wasn’t able to replicate the same issue with the internal site links so far.

However, you can check if adding .htaccess rules for bypassing the password protection helps:
https://stackoverflow.com/questions/10419592/htaccess-htpasswd-bypass-if-at-a-certain-ip-address

For the Local version try it with the IP address of your site. Usually you can find it in the hosting panel, or by visiting a site like https://whatismyipaddress.com/

For the Cloud version you can try bypassing it for these ones:

18.204.159.253
54.227.51.40
3.93.131.0
165.227.127.103
64.176.196.23
144.202.86.106

Best Regards,
Dmytro

Hi @badro0,

Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to open a new thread if you have new queries.

Best Regards
Nithin