starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 10:38:41 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

INFO obtaining ipv4 address succeeded after 1 failed try #482

New Issue
Open
opened 2025-11-20 04:24:30 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:24:30 -05:00
Owner
Copy Link

Originally created by @chchia on GitHub (Jan 7, 2025).

running ddns-updater inside casaos with duckdns.org, and it got always reported as unhealthy. checking the container log and i got full of this line.

2025-01-07T03:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T03:35:41Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T04:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T04:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T05:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T05:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T06:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T06:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T07:05:41Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T07:35:43Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T08:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T08:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T09:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T09:35:41Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T10:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T10:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T11:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T11:35:43Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T12:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T12:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T13:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T13:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T14:05:41Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T14:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T15:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try

2025-01-07T15:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try

and here to boot up log

========================================

============= ddns-updater =============

========================================

=========== Made with ❤️ by ============

======= https://github.com/qdm12 =======

========================================

========================================

Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061)

🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose

🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose

💻 Email? quentin.mcgaw@gmail.com

💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12

2025-01-06T18:35:41Z INFO Settings summary:

├── HTTP client

|   └── Timeout: 10s

├── Update

|   ├── Period: 30m0s

|   └── Cooldown: 15m0s

├── Public IP fetching

|   ├── HTTP enabled: yes

|   ├── HTTP IP providers

|   |   └── all

|   ├── HTTP IPv4 providers

|   |   └── all

|   ├── HTTP IPv6 providers

|   |   └── all

|   ├── DNS enabled: yes

|   ├── DNS timeout: 10s

|   └── DNS over TLS providers

|       └── all

├── Resolver: use Go default resolver

├── Server

|   ├── Listening address: :8000

|   └── Root URL: /

├── Health

|   └── Server listening address: 127.0.0.1:9999

├── Paths

|   ├── Data directory: /updater/data

|   ├── Config file: /updater/data/config.json

|   └── Umask: system default

├── Backup: disabled

└── Logger

    ├── Level: info

    └── Caller: hidden

2025-01-06T18:35:41Z INFO reading JSON config from file /updater/data/config.json

2025-01-06T18:35:41Z INFO Found 5 settings to update records
Originally created by @chchia on GitHub (Jan 7, 2025). running ddns-updater inside casaos with duckdns.org, and it got always reported as unhealthy. checking the container log and i got full of this line. ``` 2025-01-07T03:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T03:35:41Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T04:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T04:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T05:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T05:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T06:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T06:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T07:05:41Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T07:35:43Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T08:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T08:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T09:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T09:35:41Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T10:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T10:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T11:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T11:35:43Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T12:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T12:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T13:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T13:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T14:05:41Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T14:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T15:05:42Z INFO obtaining ipv4 address succeeded after 1 failed try 2025-01-07T15:35:42Z INFO obtaining ipv4 address succeeded after 1 failed try ``` and here to boot up log ``` ======================================== ============= ddns-updater ============= ======================================== =========== Made with ❤️ by ============ ======= https://github.com/qdm12 ======= ======================================== ======================================== Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061) 🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose 🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose 💻 Email? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2025-01-06T18:35:41Z INFO Settings summary: ├── HTTP client | └── Timeout: 10s ├── Update | ├── Period: 30m0s | └── Cooldown: 15m0s ├── Public IP fetching | ├── HTTP enabled: yes | ├── HTTP IP providers | | └── all | ├── HTTP IPv4 providers | | └── all | ├── HTTP IPv6 providers | | └── all | ├── DNS enabled: yes | ├── DNS timeout: 10s | └── DNS over TLS providers | └── all ├── Resolver: use Go default resolver ├── Server | ├── Listening address: :8000 | └── Root URL: / ├── Health | └── Server listening address: 127.0.0.1:9999 ├── Paths | ├── Data directory: /updater/data | ├── Config file: /updater/data/config.json | └── Umask: system default ├── Backup: disabled └── Logger ├── Level: info └── Caller: hidden 2025-01-06T18:35:41Z INFO reading JSON config from file /updater/data/config.json 2025-01-06T18:35:41Z INFO Found 5 settings to update records ```
saavagebueno commented 2025-11-20 04:24:31 -05:00
Author
Owner
Copy Link

@chchia commented on GitHub (Jan 18, 2025):

2025-01-18T18:33:09Z ERROR obtaining ipv4 or ipv6 address: after 3 tries, errors were: dial tcp 1.0.0.1:853: connect: connection refused, Get "[https://ipleak.net/json"](https://ipleak.net/json%22);: context deadline exceeded, dial tcp 208.67.220.220:853: connect: connection refused

it seems that the problem is here, there is a extra " (%22) after json, perhaps it should end with / ?
or maybe the sequence of "] need to change to ]" ???

Image

@chchia commented on GitHub (Jan 18, 2025): ```2025-01-18T18:33:09Z ERROR obtaining ipv4 or ipv6 address: after 3 tries, errors were: dial tcp 1.0.0.1:853: connect: connection refused, Get "[https://ipleak.net/json"](https://ipleak.net/json%22);: context deadline exceeded, dial tcp 208.67.220.220:853: connect: connection refused``` it seems that the problem is here, there is a extra " (%22) after json, perhaps it should end with / ? or maybe the sequence of "] need to change to ]" ??? ![Image](https://github.com/user-attachments/assets/2b1b2355-4142-4b14-a2b6-8c078bf03eb5)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#482
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?