Issue with HTTP Request node: Connection closed unexpectedly when calling api-data.line.me

Questions
1

I am encountering a persistent error with my HTTP Request node while trying to fetch content from the LINE Messaging API.
The Error Message: The connection to the server was closed unexpectedly, perhaps it is offline. You can retry the request immediately or wait and retry later.
Details of the Request:
Target URL: https://api-data.line.me/v2/bot/message/{messageId}/content
Method: GET
Authentication: Header Auth (Bearer Token)
Platform: n8n Cloud (or your specific setup)
What I have checked:
The API credentials and URL structure are correct.
The workflow functions correctly in other environments, but fails here.
It seems to be a network-level rejection or a firewall blocking the connection to api-data.line.me.
Could you please check if this domain is being blocked by the n8n cloud infrastructure or if there are any proxy/firewall rules I need to be aware of?
Thank you for your assistance.

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

hello @Kongsavanh_Chanthavo

usually such messages mean that the api-data.line.me is blocking access from the n8n subnets. You can reach out to them and ask to check if the subnets are being blocked.

3

Hi @Kongsavanh_Chanthavo, welcome to the n8n community :tada: ! From what I can see, this endpoint closes the connection when called from cloud IPs, which is why it works locally but fails on n8n Cloud. The practical fix is to fetch the content from a self hosted instance or through your own proxy and then pass it to n8n, since changing the HTTP Request node settings will not resolve it.