talk - fix eternal relay-ip #3217
Conversation
Signed-off-by: Simon L <[email protected]>
| IPv4_ADDRESS_TALK="$(dig nextcloud-aio-talk IN A +short | grep '^[0-9.]\+$' | sort | head -n1)" | ||
| IPv6_ADDRESS_TALK="$(dig nextcloud-aio-talk AAAA +short | grep '^[0-9a-f:]\+$' | sort | head -n1)" |
There was a problem hiding this comment.
Are these two always the container IP addresses?
There was a problem hiding this comment.
Gotcha. In that case, I propose additional changes in the upcoming comment.
|
Follow up (#3217 (comment)) I now understand your setup better, it wasn't totally clear for me. As you relay internally between eturnal and your talk component, you do not need a publicly facing IP address as a relay address. I run a similar setup in a kubernetes setup ;) Therefore, I suggest to eliminate the STUN lookup as well from your Dockerfile, use the 2nd option from here #2855 (comment) The STUN query would return an external IP address, which will let your setup fail I guess in 99,99% of the cases, because your container is not reachable publicly on the relay port range P.S. And you can leave away the |
Signed-off-by: Simon L <[email protected]>
|
Thank you both! :) |
Follow-up to #2855
cc @sando38