Couldn't call service webhook via internal domain
theo-nejm
HOBBYOP

10 months ago

I wanna my services to communicate via internal domain. It is not working for some reason, but when I use the public domain, it works well.

Solved

27 Replies

theo-nejm
HOBBYOP

10 months ago

75f448f4-88c9-4d82-b428-61740d90e40c


theo-nejm
HOBBYOP

10 months ago

I have a front-end in next - that haves a server side api calls. When I try to use internal domain to make this api calls, it doesnt work.


theo-nejm
HOBBYOP

10 months ago

My services can't communicate with each other as well. I'm trying to call a webhook on n8n and return a webhook too, it does not work as well.


theo-nejm
HOBBYOP

10 months ago

75f448f4-88c9-4d82-b428-61740d90e40c


10 months ago

are they all on the same project? in chit-chat you mentioned workspace


theo-nejm
HOBBYOP

10 months ago

yes


theo-nejm
HOBBYOP

10 months ago

all in same project


theo-nejm
HOBBYOP

10 months ago

should I specify http/https on api calls?


theo-nejm
HOBBYOP

10 months ago

ive tried both, none worked


theo-nejm
HOBBYOP

10 months ago

do i need to specify the port as well?


10 months ago

afaik and according to docs you need to specify the port when using private domains



theo-nejm
HOBBYOP

10 months ago

there is a famous template called n8n w/ workers


theo-nejm
HOBBYOP

10 months ago

you know if this is configured by default on it?


10 months ago

It is, the only connection that uses the public domain is the redis connection as stated in the template description


theo-nejm
HOBBYOP

10 months ago

why is it?


theo-nejm
HOBBYOP

10 months ago

i have redis configured as well on my project, my nest service consumes it


theo-nejm
HOBBYOP

10 months ago

via internal domain


theo-nejm
HOBBYOP

10 months ago

i wanted to avoid using public domain as much as possible


theo-nejm
HOBBYOP

10 months ago

well, the main need was fixed


theo-nejm
HOBBYOP

10 months ago

thank you, @Medim


10 months ago

some redis related issue


10 months ago

n8n does not currently support connecting to Redis over Railways ipv6 only internal network. Until a resolution is implemented, you will be charged egress fees for the Redis service.


10 months ago

can I mark this thread as solved?


theo-nejm
HOBBYOP

10 months ago

yes, please


10 months ago

!s


Status changed to Solved medim 10 months ago


10 months ago

@Jack - can you remove that from the overview since n8n does support redis via ipv6 now


Loading...