Hi Guys! I m new. Sorry for my English, its rusty.
I’m trying to read my inbox, but I can’t reach the server, because of the error I can see. I created the entry in the / etc / hosts of the Docker, but a so did not succeed. If I ping, from the Docker, I have no problems. Even so, I cannot access the Mailbox.
Very sorry but sadly not the slightest idea right now what could be wrong if you can reach it fine via the command line. Very strange problem. If I can think of anything I get back to you but to be honest the chance is small. You probably really have to keep on debugging. Sorry.
n8n does not write any logs that could be watched.
This is working for me (detecting host at terminal).
Have you tried to point to your imap server by ip? I assume it’s something related by DNS resolution (no idea why because inside container dns is working properly).
I have launched this entering my docker container this way:
# docker exec -ti YOURCONTAINERIDINDOCKER /bin/sh
# ping imap.hostinger.com.ar
PING imap.hostinger.com.ar (153.92.2.13): 56 data bytes
64 bytes from 153.92.2.13: seq=0 ttl=54 time=7.477 ms
# nc -zv imap.hostinger.com.ar 143
imap.hostinger.com.ar (153.92.2.13:143) open
Probe from Docker termination and as you told me, I have no DNS problems. I resolve the IP address.
I tried to connect to the server with IP and I arrived, but I have certificate problems. Logically.
When I try to do it by FQDN, I get these errors.
Blockquote ERROR: connection timed out. timeout = 3000 ms
ConnectionTimeoutError: connection timed out. timeout = 3000 ms
at Connection.imapOnError (/usr/local/lib/node_modules/n8n/node_modules/imap-simple/lib/imapSimple.js:544:23)
at Object.onceWrapper (events.js:417:26)
at Connection.emit (events.js:310:20)
at Timeout._onTimeout (/usr/local/lib/node_modules/n8n/node_modules/imap/lib/Connection.js:141:12)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
Hi @Santiago_Fernandez,
Presumably you’re not still facing this issue after about a year, but for others that may come across.
I was encountering the same error message, and discovered that the issue in my case was that when copy/pasting the host name into n8n, there was a ‘trailing’ space after the host. Not very easy to see. But that resolved the issue for me. I was able even able to reproduce the error message when I put the space back.
Also, @jan, typically a trailing space from a field would be omitted or otherwise not interfere in backend, so perhaps it’s something you may want to look at.
I just had the same problem and spent hours of work to realize I had a trailing space before the string. " smtp.hostinger.com". I guess you guys could make a PR to catch this problem as well.