From 8e81e967fcdc3321f924c1689b295608b86ac3a7 Mon Sep 17 00:00:00 2001 From: "Sure Admin (bot)" Date: Wed, 8 Apr 2026 18:32:43 +0200 Subject: [PATCH] docs: add Yahoo Finance IPv6 troubleshooting note (#1404) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * test push * remove test file * docs: add Yahoo Finance IPv6 troubleshooting note to compose.example.yml In Podman/IPv6 environments, DNS may resolve fc.yahoo.com to an IPv6 address first. Since IPv6 is often not configured in containers, the connection hangs instead of falling back to IPv4. Thanks to @IndicareLeve for identifying and sharing the fix. * Revise IPv6 connection notes in compose.example.yml Light edits Signed-off-by: Juan José Mata --------- Signed-off-by: Juan José Mata Co-authored-by: SureBot Co-authored-by: Juan José Mata --- compose.example.yml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/compose.example.yml b/compose.example.yml index b52c047e1..ea45dc858 100644 --- a/compose.example.yml +++ b/compose.example.yml @@ -26,6 +26,21 @@ # # https://github.com/we-promise/sure/discussions/categories/general # +# IPv6 Note (Yahoo Finance Sync, others?): +# ---------------------------------------- +# If you encounter "Failed to open TCP connection" errors to hosts like +# fc.yahoo.com in your environment, the issue may be that DNS resolves +# to an IPv6 address first. Since IPv6 may not be configured in the container, +# the connection hangs. To work around this, you can hardcode the IPv4 +# addresses in your container's /etc/hosts or set custom DNS: +# +# extra_hosts: +# - "fc.yahoo.com:173.223.12.81" +# - "query1.finance.yahoo.com:98.136.48.169" +# - "query2.finance.yahoo.com:98.136.48.169" +# +# Or use explicit DNS servers that prefer IPv4 (already configured below). +# x-db-env: &db_env POSTGRES_USER: ${POSTGRES_USER:-sure_user}