Notifications
Clear all
Topic starter
Describe the problem/error/question
I am attempting to call the Airtable API using a self-hosted version of callin.io.
Everything was functioning correctly until yesterday at 11:10 AM (GMT+2).
Since then, regardless of the request I attempt, I receive the following error: “EHOSTUNREACHABLE - The host is unreachable, perhaps the server is offline”.
Requests work fine when made through Postman or the callin.io cloud version.
Additionally, all other requests made with self-hosted callin.io are working correctly; only the Airtable API is affected.
I tried making the call using the HTTP request node, and encountered the same error.
What is the error message (if any)?
EHOSTUNREACHABLE
The host is unreachable, perhaps the server is offline
Please share your workflow
Share the output returned by the last node
{
"errorMessage": "The host is unreachable, perhaps the server is offline",
"errorDetails": {
"rawErrorMessage": [
"connect EHOSTUNREACH 2600:1f18:7473:c207:cf13:151d:ad0f:6909:443",
"connect EHOSTUNREACH 2600:1f18:7473:c207:cf13:151d:ad0f:6909:443"
],
"httpCode": "EHOSTUNREACH"
},
"n8nDetails": {
"nodeName": "HTTP Request",
"nodeType": "n8n-nodes-base.httpRequest",
"nodeVersion": 4.2,
"itemIndex": 0,
"time": "01/04/2025 11:06:04",
"n8nVersion": "1.85.1 (Self Hosted)",
"binaryDataMode": "filesystem",
"stackTrace": [
"NodeApiError: The host is unreachable, perhaps the server is offline",
" at ExecuteContext.requestWithAuthentication (/var/www/n8n/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1421:10)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at ExecuteContext.requestWithAuthentication (/var/www/n8n/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1707:11)"
]
}
}
Information on your callin.io setup
- callin.io version: 1.85.1
- Database (default: SQLite): postgres
- callin.io EXECUTIONS_PROCESS setting (default: own, main): not sure
- Running callin.io via (Docker, npm, callin.io cloud, desktop app): Yunohost
- Operating system: not sure
instance information
Debug info
core
- n8nVersion: 1.85.1
- platform: npm
- nodeJsVersion: 20.18.3
- database: postgres
- executionMode: regular
- concurrency: -1
- license: community
- consumerId: unknown
storage
- success: none
- error: all
- progress: true
- manual: false
- binaryMode: filesystem
pruning
- enabled: true
- maxAge: 168 hours
- maxCount: 2000 executions
client
- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64; rv:136.0) gecko/20100101 firefox/136.0
- isTouchDevice: false
Generated at: 2025-04-01T09:07:05.307Z
Posted : 01/04/2025 9:09 am
Hi, are you attempting to establish a connection using IPv6?
For testing purposes, could you ping a functioning machine and manually input the IP address to observe any changes?
When I attempt it here, I receive:
api.airtable.com [52.0.194.120]
You could try accessing https://52.0.194.120/v0/meta/bases
If this works, you should enforce the host to make connections using IPv4. I'm not sure how, but that would be the approach.
Posted : 01/04/2025 11:18 am
Topic starter
Thanks a lot for your answer!
You’re right, it looks like I have an issue on my VPS, with no IPv6 configured.
I cannot force the host to accept IPv4, so I’d probably better resolve this IPv6 issue on my side.
Posted : 02/04/2025 6:32 pm
Topic starter
Hello!
All issues have been fixed after setting up an IPv6 address.
There was a migration on our VPS that caused IPv6 to be disabled without our awareness.
Hope this helps!
Thanks again!
Posted : 03/04/2025 9:18 am
This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.
Posted : 10/04/2025 9:18 am