-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure https://searx.bar #102
Comments
|
I'm not sure if that's the issue. The identical configuration happens to work for a different instance of mine: https://search.zevlee.me. Perhaps it has to do with the .bar TLD for whatever reason? Edit: I just installed the cryptcheck program for myself and found that https://searx.bar is able to be resolved just fine. I think searx's cryptcheck might have blacklisted the https://searx.bar domain.
|
I took the issue over to the cryptcheck repo, and they were able to solve the problem. The website https://cryptcheck.fr is able to scan https://searx.bar fine now, so hopefully the version used for this repo will be able to as well. |
Hello, I maintain https://searx.bar and it looks like there's something that's causing the HTTPS check to trip up when scanning it. As far as I'm aware, users are able to access my instance, and other websites like the ones listed below are able to scan it just fine. Is there something that I need to do to my configuration to allow the HTTPS check to work properly? The instance is installed with searx-docker on Ubuntu Minimal 20.04. It has only what I needed to get the instance running.
Results from other websites:
Mozilla Observatory results
SSL Labs results
Security Headers results
The text was updated successfully, but these errors were encountered: