Closed davidcollini closed 2 years ago
This should be a setting in general that's off by default
You don't want support for Cloudflare? Why?
Lemme explain my problem a bit more, sites that use cloudflare sometimes block Tor connections completely, and I have auto redirect of offline instances on, but I'm stuck on a page that doesn't work unless I change the instance
For example of a url or details about a request?
Any way to fix that problem would be fine
Why though?
This is a whoogle instance
Does this setting help Auto Redirect of offline instances
? It's in the generals tab.
It does not, it should detect that even when the cloudflare server is up, the main website has to be up aswell
Even pressing update instances in settings doesn't fix it
I think it detects that the page is offline but can't redirect as it has no url so you'll think it didn't detect it.
But shouldn't the site go away when pressing Update instances
oh you're right, the url hasn't changed. Is that instance in your custom list in the extension?
It's not, it's a default
Add to the custom instances so it can detect that it's one of your instances.
Add to the custom instances so it can detect that it's one of your instances.
Why should I be adding it to custom instances and what do you mean that it's one of my instances
How will LibRedirect know that this is a SearX instance otherwise? It should be in the list to declare that this is one of the SearX instances. If it became offline, LibRedirect will know that this offline site is in fact one of my SearX instances so I should redirect to another online instance.
This instance was already listed as a Whoogle instance, so I shouldn't need to add it to my instances
oh sorry, was looking at the SearX list instead of whoogle's. my bad
I didn't get the cloudflare error until I added a search query, but it did auto redirect fine from it. This is from the last version 1.5.0
I see this issue is about Cloudflare downtime, but I also have a small opinion on Cloudflare that I think I should say it out, despite not relating to the downtime.
I see Libredirect currently has no option with Cloudflare, so I'm not sure if this will burden @ManeraKai with too much work, but how about adding a label to indicate which instance is on Cloudflare so that people can make up their mind (Take Piped for example, mint.lgbt is hosted on Ovh while the rest are on Cloudflare)
@whatbh I may add this feature, but I should finish the other issues first 👍
Cool! Take your time. Thanks a lot.
Maybe in the meantime I can help to filter the host in the following list. I dunno, hope it helps.
Keep this open or open a new issue that has Cloudflare instances declaration feature.
Is the first reported issue still present, or should the extension now redirect offline Cloudflare instances to a working instance and I should open a new issue about it not doing so on my end?
What's the instance that it's not redirecting?
So far, teddit.kavin.rocks. The extension sometimes redirects to it and just leaves it there.
I was trying to strict this automatic function as because of previous issues. I stricted it to just 503
504
status codes. I'll add 502
too.
The only lists that add a declaration that if the instance is using cloud flare or not are bibliogram, libreddit.
Though I found this website: https://cloudflare.hellafast.digital/
Made this script: is_cloudflare.py
import socket
import subprocess
def isCloudflare(url):
x = urlparse(url)
ip = socket.gethostbyname(x.hostname)
r = requests.get('https://www.cloudflare.com/ips-v4')
myList = r.text.split('\n')
for i in myList:
out = subprocess.run(["sh", "./src/instances/get_possible_ips.sh", i], capture_output=True, text=True)
if ip in out.stdout.splitlines():
return True
return False
print(isCloudflare('https://bib.actionsack.com'))
possible_ips.sh
nmap -sL -n $1 | awk '/Nmap scan report/{print $NF}'
And it's working!
Is there a way to automatically detect if a frontend uses Cloudflare and disable ones that do