if i try your http request to https://www.britishcouncil.org.au/ it works. What version of n8n are you using to get a timeout. Are you running the desktop app, are you using n8n cloud or do you self-host n8n?
Yep it works no problem on the desktop app, so must be an issue with the self hosted version we’re using. The self hosted version allows us to run the HTTP request for every other website I’ve tried, though (e.g. https://www.google.com)
Thanks for your solution re digital ocean. I have tried that and get this error:
I think @marcus wants you to run that command locally rather than on the Digital Ocean droplet itself. That error is saying you already have port 5678 listening locally, If you wanted to fix that I would just change the port parameter and use something like -p 5679:5678 instead.
To then access n8n it would be IP:5679 instead of IP:5678.
Hey pb, @jon was right, I just wanted to see if your http request works outside of your digital ocean setup. Now that you have run n8n mapping host port 5679 to docker port 5678 you access your n8n using your digital ocean ip address with port 5679, e.g. 126.96.36.199.:5679
Now that we have established that https://www.britishcouncil.org.au/ is working outside of your digital ocean droplet, the problem seems to be network related and not n8n related. Why it’s not working I don’t know. If you did make lot’s of requests your IP adress could have been blocked or rate limited for some time. But that is just a guess
Hey pb, sorry I tried it out several ways and it works for me. It’s especially hard to retrace since you are getting a timeout instead of an error. Do you experience this problem with any other website or is it just the britishcouncil page?