Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Stuck in the 'Deploying' STate #900

Open
khowe085 opened this issue Jan 2, 2025 · 3 comments
Open

Bug: Stuck in the 'Deploying' STate #900

khowe085 opened this issue Jan 2, 2025 · 3 comments

Comments

@khowe085
Copy link

khowe085 commented Jan 2, 2025

TLDR: I deployed the application to TrueNAS Scale v24.10 and it is stuck in the 'deploying' state even though it is actively updating my IP address as expected

  1. Is this urgent: No
  2. DNS provider(s) you use: CloudFlare
  3. Program version: 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)
  4. What are you using to run the container: TrueNAS Scale community apps
  5. Extra information (optional):

AFAIK This version of TrueNAS scale is using docker. They have a UI system that provides fields and then builds the container (presumably with docker compose) from that input. I haven't been able to find the actual yaml file in the UI though.

Logs:

2025-01-02 03:26:30.180094+00:00========================================
2025-01-02 03:26:30.180127+00:00========================================
2025-01-02 03:26:30.180140+00:00============= ddns-updater =============
2025-01-02 03:26:30.180150+00:00========================================
2025-01-02 03:26:30.180161+00:00=========== Made with ❤️ by ============
2025-01-02 03:26:30.180180+00:00======= https://github.com/qdm12 =======
2025-01-02 03:26:30.180190+00:00========================================
2025-01-02 03:26:30.180201+00:00========================================
2025-01-02 03:26:30.180211+00:002025-01-02T03:26:30.180211778Z
2025-01-02 03:26:30.180222+00:00Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)
2025-01-02 03:26:30.180239+00:002025-01-02T03:26:30.180239967Z
2025-01-02 03:26:30.180250+00:00🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose
2025-01-02 03:26:30.180261+00:00🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose
2025-01-02 03:26:30.180272+00:00💻 Email? [email protected]
2025-01-02 03:26:30.180289+00:00💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2025-01-02 03:26:30.180751+00:002025-01-01T22:26:30-05:00 INFO Settings summary:
2025-01-02 03:26:30.180772+00:00├── HTTP client
2025-01-02 03:26:30.180785+00:00|   └── Timeout: 10s
2025-01-02 03:26:30.180806+00:00├── Update
2025-01-02 03:26:30.180817+00:00|   ├── Period: 5m0s
2025-01-02 03:26:30.180827+00:00|   └── Cooldown: 5m0s
2025-01-02 03:26:30.180838+00:00├── Public IP fetching
2025-01-02 03:26:30.180848+00:00|   ├── HTTP enabled: yes
2025-01-02 03:26:30.180859+00:00|   ├── HTTP IP providers
2025-01-02 03:26:30.180877+00:00|   |   └── all
2025-01-02 03:26:30.180888+00:00|   ├── HTTP IPv4 providers
2025-01-02 03:26:30.180898+00:00|   |   └── all
2025-01-02 03:26:30.180909+00:00|   ├── HTTP IPv6 providers
2025-01-02 03:26:30.180919+00:00|   |   └── all
2025-01-02 03:26:30.180937+00:00|   ├── DNS enabled: yes
2025-01-02 03:26:30.180948+00:00|   ├── DNS timeout: 3s
2025-01-02 03:26:30.180958+00:00|   └── DNS over TLS providers
2025-01-02 03:26:30.180969+00:00|       └── all
2025-01-02 03:26:30.180979+00:00├── Resolver: use Go default resolver
2025-01-02 03:26:30.180996+00:00├── Server
2025-01-02 03:26:30.181007+00:00|   ├── Listening address: :30007
2025-01-02 03:26:30.181017+00:00|   └── Root URL: /
2025-01-02 03:26:30.181028+00:00├── Health
2025-01-02 03:26:30.181038+00:00|   └── Server listening address: 127.0.0.1:9999
2025-01-02 03:26:30.181056+00:00├── Paths
2025-01-02 03:26:30.181067+00:00|   ├── Data directory: /updater/data
2025-01-02 03:26:30.181077+00:00|   ├── Config file: /updater/data/config.json
2025-01-02 03:26:30.181088+00:00|   └── Umask: --------w-
2025-01-02 03:26:30.181098+00:00├── Backup
2025-01-02 03:26:30.181116+00:00|   ├── Period: 24h0m0s
2025-01-02 03:26:30.181127+00:00|   └── Directory: /updater/data
2025-01-02 03:26:30.181137+00:00└── Logger
2025-01-02 03:26:30.181148+00:00├── Level: info
2025-01-02 03:26:30.181160+00:00└── Caller: hidden
2025-01-02 03:26:30.181187+00:002025-01-01T22:26:30-05:00 INFO reading JSON config from environment variable CONFIG
2025-01-02 03:26:30.181574+00:002025-01-01T22:26:30-05:00 INFO Found single setting to update record
2025-01-02 03:26:30.305828+00:002025-01-01T22:26:30-05:00 INFO Reading history from database: domain {domain} owner @ ipv4 or ipv6
2025-01-02 03:26:30.306359+00:002025-01-01T22:26:30-05:00 INFO [healthcheck server] health http server listening on 127.0.0.1:9999
2025-01-02 03:26:30.306458+00:002025-01-01T22:26:30-05:00 INFO [http server] http server listening on [::]:30007
2025-01-02 03:26:30.306524+00:002025-01-01T22:26:30-05:00 INFO [backup] each 24h0m0s; writing zip files to directory /updater/data
2025-01-02 03:26:31.044362+00:002025-01-01T22:26:31-05:00 INFO IP address of {domain} is {privateIP} and your IP address is {publicIP}
2025-01-02 03:26:31.044453+00:002025-01-01T22:26:31-05:00 INFO Updating record [domain: {domain} | owner: @ | provider: cloudflare | ip: ipv4 or ipv6] to use {publicIP}
2025-01-02 03:26:38.638178+00:002025/01/01 22:26:38 "GET http://{privateIP}:30007/ HTTP/1.1" from {privateIP} - 200 2488B in 290.652µs
2025-01-02 03:26:38.672136+00:002025/01/01 22:26:38 "GET http://{privateIP}:30007/static/styles.css HTTP/1.1" from {privateIP} - 200 3203B in 463.907µs
2025-01-02 03:26:38.704469+00:002025/01/01 22:26:38 "GET http://{privateIP}:30007/static/favicon.svg HTTP/1.1" from {privateIP} - 200 3192B in 90.298µs

Host OS: TrueNAS Scale v24.10

@briveramelo
Copy link

also experiencing this on TrueNAS Scale v24.10, same conditions

@haldi4803
Copy link

haldi4803 commented Jan 2, 2025

2025-01-02 17:17:53.816655+00:00========================================
2025-01-02 17:17:53.816703+00:00========================================
2025-01-02 17:17:53.816714+00:00============= ddns-updater =============
2025-01-02 17:17:53.816721+00:00========================================
2025-01-02 17:17:53.816728+00:00=========== Made with ❤️ by ============
2025-01-02 17:17:53.816741+00:00======= https://github.com/qdm12 =======
2025-01-02 17:17:53.816749+00:00========================================
2025-01-02 17:17:53.816755+00:00========================================
2025-01-02 17:17:53.816762+00:002025-01-02T17:17:53.816762493Z
2025-01-02 17:17:53.816769+00:00Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)
2025-01-02 17:17:53.816779+00:002025-01-02T17:17:53.816779707Z
2025-01-02 17:17:53.816787+00:00🔧 Need help? ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new/choose
2025-01-02 17:17:53.816794+00:00🐛 Bug? ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new/choose
2025-01-02 17:17:53.816801+00:00💻 Email? [email protected]
2025-01-02 17:17:53.816812+00:00💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2025-01-02 17:17:53.816907+00:002025-01-02T18:17:53+01:00 INFO Settings summary:
2025-01-02 17:17:53.816927+00:00├── HTTP client
2025-01-02 17:17:53.816936+00:00|   └── Timeout: 10s
2025-01-02 17:17:53.816950+00:00├── Update
2025-01-02 17:17:53.816959+00:00|   ├── Period: 5m0s
2025-01-02 17:17:53.816966+00:00|   └── Cooldown: 5m0s
2025-01-02 17:17:53.816973+00:00├── Public IP fetching
2025-01-02 17:17:53.816980+00:00|   ├── HTTP enabled: yes
2025-01-02 17:17:53.816987+00:00|   ├── HTTP IP providers
2025-01-02 17:17:53.816998+00:00|   |   └── all
2025-01-02 17:17:53.817005+00:00|   ├── HTTP IPv4 providers
2025-01-02 17:17:53.817012+00:00|   |   └── all
2025-01-02 17:17:53.817019+00:00|   ├── HTTP IPv6 providers
2025-01-02 17:17:53.817026+00:00|   |   └── all
2025-01-02 17:17:53.817036+00:00|   ├── DNS enabled: yes
2025-01-02 17:17:53.817044+00:00|   ├── DNS timeout: 3s
2025-01-02 17:17:53.817050+00:00|   └── DNS over TLS providers
2025-01-02 17:17:53.817057+00:00|       └── cloudflare
2025-01-02 17:17:53.817064+00:00├── Resolver: use Go default resolver
2025-01-02 17:17:53.817074+00:00├── Server
2025-01-02 17:17:53.817081+00:00|   ├── Listening address: :30000
2025-01-02 17:17:53.817088+00:00|   └── Root URL: /
2025-01-02 17:17:53.817095+00:00├── Health
2025-01-02 17:17:53.817101+00:00|   └── Server listening address: 127.0.0.1:9999
2025-01-02 17:17:53.817132+00:00├── Paths
2025-01-02 17:17:53.817141+00:00|   ├── Data directory: /updater/data
2025-01-02 17:17:53.817148+00:00|   ├── Config file: /updater/data/config.json
2025-01-02 17:17:53.817155+00:00|   └── Umask: --------w-
2025-01-02 17:17:53.817161+00:00├── Backup
2025-01-02 17:17:53.817172+00:00|   ├── Period: 24h0m0s
2025-01-02 17:17:53.817180+00:00|   └── Directory: /updater/data
2025-01-02 17:17:53.817186+00:00└── Logger
2025-01-02 17:17:53.817193+00:00├── Level: info
2025-01-02 17:17:53.817200+00:00└── Caller: hidden
2025-01-02 17:17:53.817210+00:002025-01-02T18:17:53+01:00 INFO reading JSON config from environment variable CONFIG
2025-01-02 17:17:53.817219+00:002025-01-02T18:17:53+01:00 INFO reading JSON config from file /updater/data/config.json
2025-01-02 17:17:53.817227+00:002025-01-02T18:17:53+01:00 WARN Found no setting to update record
2025-01-02 17:17:53.860899+00:002025-01-02T18:17:53+01:00 INFO [healthcheck server] health http server listening on 127.0.0.1:9999
2025-01-02 17:17:53.860983+00:002025-01-02T18:17:53+01:00 INFO [http server] http server listening on [::]:30000
2025-01-02 17:17:53.861020+00:002025-01-02T18:17:53+01:00 INFO [backup] each 24h0m0s; writing zip files to directory /updater/data
2025-01-02 17:21:14.519865+00:002025/01/02 18:21:14 "GET http://elitedesk.netbird.selfhosted:30000/ HTTP/1.1" from 172.16.4.1:59887 - 200 1907B in 31.418µs
2025-01-02 17:21:14.577275+00:002025/01/02 18:21:14 "GET http://elitedesk.netbird.selfhosted:30000/static/styles.css HTTP/1.1" from 172.16.4.1:59887 - 200 3203B in 256.593µs
2025-01-02 17:21:14.617148+00:002025/01/02 18:21:14 "GET http://elitedesk.netbird.selfhosted:30000/static/favicon.svg HTTP/1.1" from 172.16.4.1:59887 - 200 3192B in 110.095µs
2025-01-02 17:28:32.469756+00:002025/01/02 18:28:32 "GET http://elitedesk.netbird.selfhosted:30000/ HTTP/1.1" from 172.16.4.1:60163 - 200 1907B in 67.033µs
2025-01-02 17:28:32.527468+00:002025/01/02 18:28:32 "GET http://elitedesk.netbird.selfhosted:30000/static/styles.css HTTP/1.1" from 172.16.4.1:60163 - 200 3203B in 287.053µs
2025-01-02 17:28:32.565613+00:002025/01/02 18:28:32 "GET http://elitedesk.netbird.selfhosted:30000/static/favicon.svg HTTP/1.1" from 172.16.4.1:60163 - 200 3192B in 316.402µs

it's running well, except:

2025-01-02 17:17:53.817210+00:002025-01-02T18:17:53+01:00 INFO reading JSON config from environment variable CONFIG
2025-01-02 17:17:53.817219+00:002025-01-02T18:17:53+01:00 INFO reading JSON config from file /updater/data/config.json
2025-01-02 17:17:53.817227+00:002025-01-02T18:17:53+01:00 WARN Found no setting to update record

config.json gets overwritten everytime the container starts...
Scale v24.10

Edit: There is now a "Config" option in TrueNAS... so config.json is deprecated -.-

@khowe085
Copy link
Author

khowe085 commented Jan 9, 2025

Crossed-posted this with the Over at TrueNAS apps. Give it a read @haldi4803.

Turns out that, for me anyway, this is because I have a custom DNS rule on my router that loops my domain back to the the local server. DDNS-Updater doesn't like that, and in turn fails the health check that determines if the app is running or still deploying. They closed the issue as it 'behaves as intended' from the view of TrueNAS Apps.

From a DDNS-Updater perspective, I don't know why it doesn't like it when I have this rule in place. I would argue that this should probably be logged as a warning rather than failing the health check. In mu case this rule was setup so that I can access my apps through a reverse proxy (on the NAS), using my public domain / certs, without having to permanently open port 443.

Here is the error that the related to the health check failure.

2025-01-07T21:09:50-05:00 ERROR program is unhealthy: lookup IP addresses do not match: {NAS private IP} instead of {my public IP} for {mydomain}\n\n2025-01-07T21:09:50-05:00 INFO Shutdown successful\n

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants