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

Bug: Stuck at "deploying" in TrueNAS Scale but app works as expected #536

New Issue
Open
opened 2025-11-20 04:24:47 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:24:47 -05:00
Owner
Copy Link

Originally created by @nicolajkl on GitHub (Jun 25, 2025).

TLDR: Describe your issue in a one liner here

When I add configs to the app, it gets stuck on "deploying", but everything works as expected; my domains gets updated successfully, and the web interface is running.
I'm running it as a custom user; UUID: 3000, GUID: 3000.

I've marked the issue as "not urgent" since everything works.
It's just annoying that it keeps saying "deploying" in the TrueNAS apps section.

  1. Is this urgent: No

  2. DNS provider(s) you use: Cloudflare

  3. Program version: 2.9.0

    Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)

  4. What are you using to run the container: docker-compose/TrueNAS Scale 25.04.1

Logs:

2025-06-26 02:57:54.518947+00:00========================================
2025-06-26 02:57:54.518977+00:00========================================
2025-06-26 02:57:54.518983+00:00============= ddns-updater =============
2025-06-26 02:57:54.518987+00:00========================================
2025-06-26 02:57:54.518991+00:00=========== Made with ❤️ by ============
2025-06-26 02:57:54.519000+00:00======= https://github.com/qdm12 =======
2025-06-26 02:57:54.519005+00:00========================================
2025-06-26 02:57:54.519008+00:00========================================
2025-06-26 02:57:54.519013+00:002025-06-26T02:57:54.519013152Z
2025-06-26 02:57:54.519017+00:00Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)
2025-06-26 02:57:54.519023+00:002025-06-26T02:57:54.519023903Z
2025-06-26 02:57:54.519028+00:00🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose
2025-06-26 02:57:54.519032+00:00🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose
2025-06-26 02:57:54.519036+00:00💻 Email? quentin.mcgaw@gmail.com
2025-06-26 02:57:54.519042+00:00💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2025-06-26 02:57:54.519426+00:002025-06-26T04:57:54+02:00 INFO Settings summary:
2025-06-26 02:57:54.519444+00:00├── HTTP client
2025-06-26 02:57:54.519454+00:00|   └── Timeout: 10s
2025-06-26 02:57:54.519470+00:00├── Update
2025-06-26 02:57:54.519480+00:00|   ├── Period: 1h0m0s
2025-06-26 02:57:54.519488+00:00|   └── Cooldown: 5m0s
2025-06-26 02:57:54.519496+00:00├── Public IP fetching
2025-06-26 02:57:54.519506+00:00|   ├── HTTP enabled: yes
2025-06-26 02:57:54.519514+00:00|   ├── HTTP IP providers
2025-06-26 02:57:54.519528+00:00|   |   └── all
2025-06-26 02:57:54.519536+00:00|   ├── HTTP IPv4 providers
2025-06-26 02:57:54.519545+00:00|   |   └── all
2025-06-26 02:57:54.519553+00:00|   ├── HTTP IPv6 providers
2025-06-26 02:57:54.519561+00:00|   |   └── all
2025-06-26 02:57:54.519575+00:00|   ├── DNS enabled: yes
2025-06-26 02:57:54.519584+00:00|   ├── DNS timeout: 3s
2025-06-26 02:57:54.519593+00:00|   └── DNS over TLS providers
2025-06-26 02:57:54.519601+00:00|       └── all
2025-06-26 02:57:54.519609+00:00├── Resolver: use Go default resolver
2025-06-26 02:57:54.519622+00:00├── Server
2025-06-26 02:57:54.519631+00:00|   ├── Listening address: :30007
2025-06-26 02:57:54.519639+00:00|   └── Root URL: /
2025-06-26 02:57:54.519647+00:00├── Health
2025-06-26 02:57:54.519655+00:00|   └── Server listening address: 127.0.0.1:9999
2025-06-26 02:57:54.519668+00:00├── Paths
2025-06-26 02:57:54.519677+00:00|   ├── Data directory: /updater/data
2025-06-26 02:57:54.519685+00:00|   ├── Config file: /updater/data/config.json
2025-06-26 02:57:54.519693+00:00|   └── Umask: --------w-
2025-06-26 02:57:54.519701+00:00├── Backup
2025-06-26 02:57:54.519715+00:00|   ├── Period: 24h0m0s
2025-06-26 02:57:54.519724+00:00|   └── Directory: /updater/data
2025-06-26 02:57:54.519732+00:00└── Logger
2025-06-26 02:57:54.519740+00:00├── Level: info
2025-06-26 02:57:54.519748+00:00└── Caller: hidden
(left out the part with my domain names)

Configuration file (remove your credentials!):

{
  "settings": [
    {
      "domain": "",
      "ip_version": "ipv4",
      "provider": "cloudflare",
      "proxied": false,
      "token": "",
      "ttl": 1,
      "zone_identifier": ""
    },
    {
      "domain": "",
      "ip_version": "ipv4",
      "provider": "cloudflare",
      "proxied": false,
      "token": "",
      "ttl": 1,
      "zone_identifier": ""
    },
    {
      "domain": "",
      "ip_version": "ipv4",
      "provider": "cloudflare",
      "proxied": false,
      "token": "",
      "ttl": 1,
      "zone_identifier": ""
    },
    {
      "domain": "",
      "ip_version": "ipv4",
      "provider": "cloudflare",
      "proxied": false,
      "token": "",
      "ttl": 1,
      "zone_identifier": ""
    }
  ]
}
(left out sensitive information, including domains)

Host OS:
Debian 12/TrueNAS Scale 25.04.1

Originally created by @nicolajkl on GitHub (Jun 25, 2025). **TLDR**: *Describe your issue in a one liner here* When I add configs to the app, it gets stuck on "deploying", but everything works as expected; my domains gets updated successfully, and the web interface is running. I'm running it as a custom user; UUID: 3000, GUID: 3000. I've marked the issue as "not urgent" since everything works. It's just annoying that it keeps saying "deploying" in the TrueNAS apps section. 1. Is this urgent: No 2. DNS provider(s) you use: Cloudflare 3. Program version: 2.9.0 <!-- See the line at the top of your logs --> `Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)` 4. What are you using to run the container: docker-compose/TrueNAS Scale 25.04.1 Logs: ```log 2025-06-26 02:57:54.518947+00:00======================================== 2025-06-26 02:57:54.518977+00:00======================================== 2025-06-26 02:57:54.518983+00:00============= ddns-updater ============= 2025-06-26 02:57:54.518987+00:00======================================== 2025-06-26 02:57:54.518991+00:00=========== Made with ❤️ by ============ 2025-06-26 02:57:54.519000+00:00======= https://github.com/qdm12 ======= 2025-06-26 02:57:54.519005+00:00======================================== 2025-06-26 02:57:54.519008+00:00======================================== 2025-06-26 02:57:54.519013+00:002025-06-26T02:57:54.519013152Z 2025-06-26 02:57:54.519017+00:00Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061) 2025-06-26 02:57:54.519023+00:002025-06-26T02:57:54.519023903Z 2025-06-26 02:57:54.519028+00:00🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose 2025-06-26 02:57:54.519032+00:00🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose 2025-06-26 02:57:54.519036+00:00💻 Email? quentin.mcgaw@gmail.com 2025-06-26 02:57:54.519042+00:00💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2025-06-26 02:57:54.519426+00:002025-06-26T04:57:54+02:00 INFO Settings summary: 2025-06-26 02:57:54.519444+00:00├── HTTP client 2025-06-26 02:57:54.519454+00:00| └── Timeout: 10s 2025-06-26 02:57:54.519470+00:00├── Update 2025-06-26 02:57:54.519480+00:00| ├── Period: 1h0m0s 2025-06-26 02:57:54.519488+00:00| └── Cooldown: 5m0s 2025-06-26 02:57:54.519496+00:00├── Public IP fetching 2025-06-26 02:57:54.519506+00:00| ├── HTTP enabled: yes 2025-06-26 02:57:54.519514+00:00| ├── HTTP IP providers 2025-06-26 02:57:54.519528+00:00| | └── all 2025-06-26 02:57:54.519536+00:00| ├── HTTP IPv4 providers 2025-06-26 02:57:54.519545+00:00| | └── all 2025-06-26 02:57:54.519553+00:00| ├── HTTP IPv6 providers 2025-06-26 02:57:54.519561+00:00| | └── all 2025-06-26 02:57:54.519575+00:00| ├── DNS enabled: yes 2025-06-26 02:57:54.519584+00:00| ├── DNS timeout: 3s 2025-06-26 02:57:54.519593+00:00| └── DNS over TLS providers 2025-06-26 02:57:54.519601+00:00| └── all 2025-06-26 02:57:54.519609+00:00├── Resolver: use Go default resolver 2025-06-26 02:57:54.519622+00:00├── Server 2025-06-26 02:57:54.519631+00:00| ├── Listening address: :30007 2025-06-26 02:57:54.519639+00:00| └── Root URL: / 2025-06-26 02:57:54.519647+00:00├── Health 2025-06-26 02:57:54.519655+00:00| └── Server listening address: 127.0.0.1:9999 2025-06-26 02:57:54.519668+00:00├── Paths 2025-06-26 02:57:54.519677+00:00| ├── Data directory: /updater/data 2025-06-26 02:57:54.519685+00:00| ├── Config file: /updater/data/config.json 2025-06-26 02:57:54.519693+00:00| └── Umask: --------w- 2025-06-26 02:57:54.519701+00:00├── Backup 2025-06-26 02:57:54.519715+00:00| ├── Period: 24h0m0s 2025-06-26 02:57:54.519724+00:00| └── Directory: /updater/data 2025-06-26 02:57:54.519732+00:00└── Logger 2025-06-26 02:57:54.519740+00:00├── Level: info 2025-06-26 02:57:54.519748+00:00└── Caller: hidden (left out the part with my domain names) ``` Configuration file (**remove your credentials!**): ```json { "settings": [ { "domain": "", "ip_version": "ipv4", "provider": "cloudflare", "proxied": false, "token": "", "ttl": 1, "zone_identifier": "" }, { "domain": "", "ip_version": "ipv4", "provider": "cloudflare", "proxied": false, "token": "", "ttl": 1, "zone_identifier": "" }, { "domain": "", "ip_version": "ipv4", "provider": "cloudflare", "proxied": false, "token": "", "ttl": 1, "zone_identifier": "" }, { "domain": "", "ip_version": "ipv4", "provider": "cloudflare", "proxied": false, "token": "", "ttl": 1, "zone_identifier": "" } ] } (left out sensitive information, including domains) ``` Host OS: Debian 12/TrueNAS Scale 25.04.1
saavagebueno commented 2025-11-20 04:24:48 -05:00
Author
Owner
Copy Link

@dj21d commented on GitHub (Aug 22, 2025):

I was having this issue until I reinstalled my app instance. There was also an internal dns issue on my side that I needed to correct (internal DNS was causing it to think the record was out of date, and it needed to keep updating it in cloudflare)

@dj21d commented on GitHub (Aug 22, 2025): I was having this issue until I reinstalled my app instance. There was also an internal dns issue on my side that I needed to correct (internal DNS was causing it to think the record was out of date, and it needed to keep updating it in cloudflare)
saavagebueno commented 2025-11-20 04:24:48 -05:00
Author
Owner
Copy Link

@luotn commented on GitHub (Sep 2, 2025):

I'm having the same issue on OS: TrueNAS Scale 25.04.2.3 using DDNS Update version 2.9.0 (or 1.2.7). Everything works as expected, but the container keeps showing "Deploying". Additionally, since the ddns and permissions containers are deploying and stopped respectively, there is no way to access the command lines.

@luotn commented on GitHub (Sep 2, 2025): I'm having the same issue on OS: TrueNAS Scale 25.04.2.3 using DDNS Update version 2.9.0 (or 1.2.7). Everything works as expected, but the container keeps showing "Deploying". Additionally, since the ddns and permissions containers are deploying and stopped respectively, there is no way to access the command lines.
saavagebueno commented 2025-11-20 04:24:48 -05:00
Author
Owner
Copy Link

@tatelax commented on GitHub (Nov 4, 2025):

I'm having the same issue on OS: TrueNAS Scale 25.04.2.3 using DDNS Update version 2.9.0 (or 1.2.7). Everything works as expected, but the container keeps showing "Deploying". Additionally, since the ddns and permissions containers are deploying and stopped respectively, there is no way to access the command lines.

As soon as you see the ddns container starting, click "view logs". if you wait longer than 5 seconds after it begins starting, you will not be able to view them.

@tatelax commented on GitHub (Nov 4, 2025): > I'm having the same issue on OS: TrueNAS Scale 25.04.2.3 using DDNS Update version 2.9.0 (or 1.2.7). Everything works as expected, but the container keeps showing "Deploying". Additionally, since the ddns and permissions containers are deploying and stopped respectively, there is no way to access the command lines. As soon as you see the ddns container starting, click "view logs". if you wait longer than 5 seconds after it begins starting, you will not be able to view them.
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#536
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?