Error Getaddrinfo EAI_AGAIN n8n on a Synology NAS

Questions
1

Hello n8n community!

I am new to n8n, I have to say… I installed it on my Synology NAS with a Docker. Everything installed find but when I’m trying to execute the node I get always same error message:

ERROR: UNKNOWN ERROR - check the detailed error for more information
getaddrinfo EAI_AGAIN api. notion .com
{

« status »: « rejected »,

« reason »: {
« message »: « getaddrinfo EAI_AGAIN api.notion. com »,

« name »: « Error »,

« stack »: « Error: getaddrinfo EAI_AGAIN api .notion. com at GetAddrInfoReqWrap.onlookup [as >oncomplete] (node:dns:71:26) »,

« code »: « EAI_AGAIN »

}

}

Here it was with the workflow I was trying to implement with Notion, but it happens also with simple http request where no credential is required.

Would someone have an idea?

n8n version: 0.169.0
Installed on NAS Synology
Docker: 20.10.3-1239

2

Hi @Philippe, welcome to the community and I am very sorry to hear you’re having trouble here.

EAI_AGAIN isn’t an n8n-specific error but suggests network problems (specifically, resolving the domain name api.notion.com seems to fail here). Is there any chance your NAS system restricts DNS lookups from docker containers or other network traffic for whatever reason? Or could this have been a temporary problem with the name resolution in your network?

3

Hello @MutedJam and many thanks for your warm welcome and swift answer!

Thanks for putting me ontrack! Indeed this must be due to bad setup in the docker, it’s a good start for me. The only thing I found out is that setting up a docker is much more complex than what I was expecting!
I have tried to look at tutorials, but nothing specific on n8n unfortunately for me and I am still stuck on it.
Could someone who experienced the installation of n8n on a NAS Synology just give me some main directions to look at ?
It would be really great, thanks a lot in advance!
Philippe

4

I don’t think we have any Synology users internally (I used to have a QNAP NAS, but that’s gone now) unfortunately, but perhaps a fellow community member will be able to help with this.

Is this specific to the Notion node or are you also running into trouble when pulling data from other sources? An easy way to test this would be the HTTP Request node, for example something like this:

5

Hello,

Just to keep you updated on my issue that I solved.
I had not setup correctly my domain within Docker, hence the issues I was getting.
Now it is solved, I can send some http requests.

Thanks anyway again!

Philippe

6

Hi Philippe! I’m having a similar issue; any guidance you can provide on how you setup the domain correctly within Docker? I’m running n8n on my Synology NAS as well.

7

Hello,
As far as I remember, I had not setup correctly the domain into docker.
By domain I mean yoiu need to create your domain like this n8n.yourname.synology.me in order to get the certificates…
But, I have found a super nice tutorial where you have a step by step guide to configure n8n with portainer it’s here: How to Install n8n on Your Synology NAS – Marius Hosting
Everything is really well explained and easy to understand (I understood myself!)
Good luck with your implementation!

8

Ahh yeah that’s the exact tutorial I used to get it up and running. Everything is working great except for the network requests out of docker.

Thanks anyway, i’ll do some more digging.

9

If you get this kind of meesage, it means that the server received a request but don’t know where to send back the answer or can’t reach the address you are sending the answer to.
Did you correctly setup the router to redirect n8n? Generally 5678…
Did you create the domain name correctly?

10

rebuilding actually fixed the issue, i may not have setup the domain name correctly the first time around.

Thank you!