starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-07-24 14:43:39 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Help: container unhealthy OVH / nochg #206

New Issue
Closed
opened 2025-11-20 04:21:31 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:21:31 -05:00
Owner
Copy Link

Originally created by @stanthewizzard on GitHub (Aug 24, 2022).

  1. Is this urgent:
  2. No
  3. DNS provider(s) you use:
  4. OVH
  5. Program version:
    Running version latest built on 2022-03-15T14:38:50Z (commit 584597d)
  6. What are you using to run the container: docker-compose
version: "3.7"
services:
  ddns-updater:
    image: qmcgaw/ddns-updater
    container_name: ddns-updater
    network_mode: bridge
    ports:
      - 8000:8000/tcp
    volumes:
      - ./data:/updater/data
    environment:
      - CONFIG=
      - PERIOD=15m
      - UPDATE_COOLDOWN_PERIOD=5m
      - PUBLICIP_FETCHERS=http
      - PUBLICIP_HTTP_PROVIDERS=ipinfo
      - PUBLICIPV4_HTTP_PROVIDERS=all
#     - PUBLICIPV6_HTTP_PROVIDERS=all
      - PUBLICIP_DNS_PROVIDERS=all
      - PUBLICIP_DNS_TIMEOUT=3s
      - HTTP_TIMEOUT=10s

      # Web UI
      - LISTENING_PORT=8000
      - ROOT_URL=/

      # Backup
      - BACKUP_PERIOD=0 # 0 to disable
      - BACKUP_DIRECTORY=/updater/data

      # Other
      - LOG_LEVEL=info
      - LOG_CALLER=hidden
      - TZ=Europe/Paris
    restart: always

Logs:

2022/08/24 07:58:42 INFO reading JSON config from file /updater/data/config.json
2022/08/24 07:58:42 INFO Found 3 settings to update records
2022/08/24 07:58:42 INFO Reading history from database: domain mail.first.com host @
2022/08/24 07:58:42 INFO Reading history from database: domain first.com host @
2022/08/24 07:58:42 INFO Reading history from database: domain dyn.second.info host @
2022/08/24 07:58:42 INFO backup: disabled
2022/08/24 07:58:42 INFO http server: listening on :8000
2022/08/24 07:58:42 INFO healthcheck server: listening on 127.0.0.1:9999
2022/08/24 07:58:42 INFO IPv4 address of mail.first.com is 192.168.0.8 and your IPv4 address is 90.7.194.22
2022/08/24 07:58:42 WARN cannot DNS resolve first.com after 5 tries: lookup first.com on 127.0.0.11:53: no such host
2022/08/24 07:58:42 INFO IPv4 address of first.com is <nil> and your IPv4 address is 90.7.194.22
2022/08/24 07:58:42 WARN cannot DNS resolve dyn.second.info after 5 tries: lookup dyn.second.info on 127.0.0.11:53: no such host
2022/08/24 07:58:42 INFO IPv4 address of dyn.second.info is <nil> and your IPv4 address is 90.7.194.22
2022/08/24 07:58:42 INFO Updating record [domain: mail.first.com | host: @ | provider: OVH] to use 90.7.194.22
2022/08/24 07:58:43 ERROR unknown response received: nochg 90.7.194.22
2022/08/24 07:58:43 INFO Updating record [domain: first.com | host: @ | provider: OVH] to use 90.7.194.22
2022/08/24 07:58:44 ERROR unknown response received: nochg 90.7.194.22
2022/08/24 07:58:44 INFO Updating record [domain: dyn.second.info | host: @ | provider: OVH] to use 90.7.194.22
2022/08/24 07:58:45 ERROR unknown response received: nochg 90.7.194.22

Configuration file (remove your credentials!):

{
  "settings": [
    {
      "provider": "ovh",
      "domain": "mail.first.com",
      "host": "@",
      "username": "first.com-stank",
      "password": "xxxxxxxxxxxxxxxxxxxxx",
      "ip_version": "ipv4",
      "provider_ip": true
    },
    {
      "provider": "ovh",
      "domain": "first.com",
      "host": "@",
      "username": "first.com-stank",
      "password": "xxxxxxxxxxxxxxxxxxxxx",
      "ip_version": "ipv4",
      "provider_ip": true
    },
    {
      "provider": "ovh",
      "domain": "dyn.second.info",
      "host": "@",
      "username": "second.info-stank",
      "password": "yyyyyyyyyyyyyyyyyyyyyyyyyyyy",
      "ip_version": "ipv4",
      "provider_ip": true
    }
  ]
}

Host OS: photon OS 4

The container is unhealthy with error nochg

Thanks for help

Originally created by @stanthewizzard on GitHub (Aug 24, 2022). 1. Is this urgent: 2. No 3. DNS provider(s) you use: 4. OVH 5. Program version: Running version latest built on 2022-03-15T14:38:50Z (commit 584597d) 6. What are you using to run the container: docker-compose ``` version: "3.7" services: ddns-updater: image: qmcgaw/ddns-updater container_name: ddns-updater network_mode: bridge ports: - 8000:8000/tcp volumes: - ./data:/updater/data environment: - CONFIG= - PERIOD=15m - UPDATE_COOLDOWN_PERIOD=5m - PUBLICIP_FETCHERS=http - PUBLICIP_HTTP_PROVIDERS=ipinfo - PUBLICIPV4_HTTP_PROVIDERS=all # - PUBLICIPV6_HTTP_PROVIDERS=all - PUBLICIP_DNS_PROVIDERS=all - PUBLICIP_DNS_TIMEOUT=3s - HTTP_TIMEOUT=10s # Web UI - LISTENING_PORT=8000 - ROOT_URL=/ # Backup - BACKUP_PERIOD=0 # 0 to disable - BACKUP_DIRECTORY=/updater/data # Other - LOG_LEVEL=info - LOG_CALLER=hidden - TZ=Europe/Paris restart: always ``` Logs: ``` 2022/08/24 07:58:42 INFO reading JSON config from file /updater/data/config.json 2022/08/24 07:58:42 INFO Found 3 settings to update records 2022/08/24 07:58:42 INFO Reading history from database: domain mail.first.com host @ 2022/08/24 07:58:42 INFO Reading history from database: domain first.com host @ 2022/08/24 07:58:42 INFO Reading history from database: domain dyn.second.info host @ 2022/08/24 07:58:42 INFO backup: disabled 2022/08/24 07:58:42 INFO http server: listening on :8000 2022/08/24 07:58:42 INFO healthcheck server: listening on 127.0.0.1:9999 2022/08/24 07:58:42 INFO IPv4 address of mail.first.com is 192.168.0.8 and your IPv4 address is 90.7.194.22 2022/08/24 07:58:42 WARN cannot DNS resolve first.com after 5 tries: lookup first.com on 127.0.0.11:53: no such host 2022/08/24 07:58:42 INFO IPv4 address of first.com is <nil> and your IPv4 address is 90.7.194.22 2022/08/24 07:58:42 WARN cannot DNS resolve dyn.second.info after 5 tries: lookup dyn.second.info on 127.0.0.11:53: no such host 2022/08/24 07:58:42 INFO IPv4 address of dyn.second.info is <nil> and your IPv4 address is 90.7.194.22 2022/08/24 07:58:42 INFO Updating record [domain: mail.first.com | host: @ | provider: OVH] to use 90.7.194.22 2022/08/24 07:58:43 ERROR unknown response received: nochg 90.7.194.22 2022/08/24 07:58:43 INFO Updating record [domain: first.com | host: @ | provider: OVH] to use 90.7.194.22 2022/08/24 07:58:44 ERROR unknown response received: nochg 90.7.194.22 2022/08/24 07:58:44 INFO Updating record [domain: dyn.second.info | host: @ | provider: OVH] to use 90.7.194.22 2022/08/24 07:58:45 ERROR unknown response received: nochg 90.7.194.22 ``` Configuration file (**remove your credentials!**): ``` { "settings": [ { "provider": "ovh", "domain": "mail.first.com", "host": "@", "username": "first.com-stank", "password": "xxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv4", "provider_ip": true }, { "provider": "ovh", "domain": "first.com", "host": "@", "username": "first.com-stank", "password": "xxxxxxxxxxxxxxxxxxxxx", "ip_version": "ipv4", "provider_ip": true }, { "provider": "ovh", "domain": "dyn.second.info", "host": "@", "username": "second.info-stank", "password": "yyyyyyyyyyyyyyyyyyyyyyyyyyyy", "ip_version": "ipv4", "provider_ip": true } ] } ``` Host OS: photon OS 4 The container is unhealthy with error nochg Thanks for help
saavagebueno commented 2025-11-20 04:21:32 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Sep 6, 2022):

Hello there. Not sure why this got closed, but 89711cd76d now accepts nochg responses and doesn't treat them as error anymore.

@qdm12 commented on GitHub (Sep 6, 2022): Hello there. Not sure why this got closed, but 89711cd76d16278cc801e71c18d3901f1781692c now accepts `nochg` responses and doesn't treat them as error anymore.
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#206
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?