However, the connection’s reliability is inconsistent. Sometimes, the request executes successfully, while other times, I receive the following error:
The connection cannot be established, this usually occurs due to an incorrect host (domain) value.
It appears that n8n is intermittently blocking the serveo.net URL, leading to these unstable responses.
Could you please investigate this issue? Specifically, is there a way to whitelist serveo.net IP addresses within n8n to prevent these connection interruptions?
{
“errorMessage”: “The connection cannot be established, this usually occurs due to an incorrect host (domain) value”,
“errorDetails”: {
“rawErrorMessage”: [
“getaddrinfo ENOTFOUND nodestack-faizan.serveo.net”,
“getaddrinfo ENOTFOUND nodestack-faizan.serveo.net”
],
“httpCode”: “ENOTFOUND”
},
“n8nDetails”: {
“nodeName”: “HTTP Request”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “23/08/2024, 11:53:35”,
“n8nVersion”: “1.53.2 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: The connection cannot be established, this usually occurs due to an incorrect host (domain) value”,
" at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:1650:33)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)“,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:673:51”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1086:20"
]
}
}
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Sorry for the delay in replying.
It doesn’t sound to me as n8n Cloud is blocking the URL.
If I understand it right serveo.net is a proxy server that creates a tunnel to your local machine allowing accessing your application/service via a public domain.
Is there any way to have n8n IPs whitelisted on that server (just in case)? Do you have access to the server logs or can ask Serveo support (if there is any) to see what happens to the requests coming from n8n Cloud? Any possibility of checking the logs on your server (in addition to Serveo’s)?
Moreover, the IP address (owned by DigitalOcean) of your custom domain is blacklisted on some services, see IP Blacklist & Email Blacklist Check.
@ihortom Thanks for your reply. I have checked the logs of serveo.net local machine but couldnt find any logs which mean n8n is not trying to hit this URL somehow.
Do you know if we have option to whitelist the domain in n8n cloud settings?
So sorry for your troubles. It looks like the DNS resolution for hostname serveo.net might fail depending on which exact nameserver gets queried. This would seem to affect not only n8n Cloud, but also happens in my local environment.
We’ll investigate further to try to and understand what’s causing this and how we might be able to mitigate it in n8n Cloud. At any rate, we’re not blocking the service on purpose.
I think we’ve found the root cause. It’s likely some DNS requests would’ve gotten blocked due to a security feature in one of our upstream DNS servers.
We have just deployed an update to the DNS configuration and initial results look promising. I’d recommend either restarting or upgrading your instance from the Admin panel, after which it should have all the most recent updates and fixes applied.
Please let me know how it looks, and if it fixes (or not) the problem for you!