QT/sure
1
0
Fork 0
mirror of https://github.com/we-promise/sure.git synced 2026-04-19 03:54:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add Yahoo Finance IPv6 troubleshooting note (#1404)

Browse Source 
* 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 <juanjo.mata@gmail.com>

---------

Signed-off-by: Juan José Mata <juanjo.mata@gmail.com>
Co-authored-by: SureBot <sure-bot@we-promise.com>
Co-authored-by: Juan José Mata <juanjo.mata@gmail.com>
This commit is contained in:
Sure Admin (bot)
2026-04-08 18:32:43 +02:00
committed by GitHub
parent 1d7c4158d4
commit 8e81e967fc
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
compose.example.yml
View File

@@ -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}