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

Bug: Can't disable UI server #418

New Issue
Closed
opened 2025-11-20 04:23:53 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:23:53 -05:00
Owner
Copy Link

Originally created by @l4l4l4l4 on GitHub (Jul 4, 2024).

Can't disable UI server

  1. Is this urgent: No
  2. DNS provider(s) you use: 8.8.8.8
  3. Program version: 2.6.1 built on 2024-06-26T19:02:48.760Z (commit 6cc0b9b)
  4. What are you using to run the container: docker-compose
  5. Extra information

Logs:

2024-07-04T23:10:14Z INFO [healthcheck server] listening on 127.0.0.1:9999
2024-07-04T23:10:14Z INFO [http server] listening on :8000

Docker inspect:

            "Env": [
                "PERIOD=60m",
                "SERVER_ENABLED=false",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "CONFIG=",
                "UPDATE_COOLDOWN_PERIOD=5m",
                "PUBLICIP_FETCHERS=all",
                "PUBLICIP_HTTP_PROVIDERS=all",
                "PUBLICIPV4_HTTP_PROVIDERS=all",
                "PUBLICIPV6_HTTP_PROVIDERS=all",
                "PUBLICIP_DNS_PROVIDERS=all",
                "PUBLICIP_DNS_TIMEOUT=3s",
                "HTTP_TIMEOUT=10s",
                "DATADIR=/updater/data",
                "RESOLVER_ADDRESS=",
                "RESOLVER_TIMEOUT=5s",
                "LISTENING_ADDRESS=:8000",
                "ROOT_URL=/",
                "BACKUP_PERIOD=0",
                "BACKUP_DIRECTORY=/updater/data",
                "LOG_LEVEL=info",
                "LOG_CALLER=hidden",
                "SHOUTRRR_ADDRESSES=",
                "SHOUTRRR_DEFAULT_TITLE=DDNS Updater",
                "TZ=",
                "HEALTH_SERVER_ADDRESS=127.0.0.1:9999",
                "HEALTH_HEALTHCHECKSIO_UUID="
            ],
Originally created by @l4l4l4l4 on GitHub (Jul 4, 2024). Can't disable UI server 1. Is this urgent: No 2. DNS provider(s) you use: 8.8.8.8 3. Program version: 2.6.1 built on 2024-06-26T19:02:48.760Z (commit 6cc0b9b) 4. What are you using to run the container: docker-compose 5. Extra information Logs: ```log 2024-07-04T23:10:14Z INFO [healthcheck server] listening on 127.0.0.1:9999 2024-07-04T23:10:14Z INFO [http server] listening on :8000 ``` Docker inspect: ```log "Env": [ "PERIOD=60m", "SERVER_ENABLED=false", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "CONFIG=", "UPDATE_COOLDOWN_PERIOD=5m", "PUBLICIP_FETCHERS=all", "PUBLICIP_HTTP_PROVIDERS=all", "PUBLICIPV4_HTTP_PROVIDERS=all", "PUBLICIPV6_HTTP_PROVIDERS=all", "PUBLICIP_DNS_PROVIDERS=all", "PUBLICIP_DNS_TIMEOUT=3s", "HTTP_TIMEOUT=10s", "DATADIR=/updater/data", "RESOLVER_ADDRESS=", "RESOLVER_TIMEOUT=5s", "LISTENING_ADDRESS=:8000", "ROOT_URL=/", "BACKUP_PERIOD=0", "BACKUP_DIRECTORY=/updater/data", "LOG_LEVEL=info", "LOG_CALLER=hidden", "SHOUTRRR_ADDRESSES=", "SHOUTRRR_DEFAULT_TITLE=DDNS Updater", "TZ=", "HEALTH_SERVER_ADDRESS=127.0.0.1:9999", "HEALTH_HEALTHCHECKSIO_UUID=" ], ```
saavagebueno commented 2025-11-20 04:23:54 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jul 5, 2024):

If you're running with Docker just don't publish the port and that's it really. The ui server won't consume any resources really if it's not accessed (and even then, it barely consumes anything).

Alternatively, upgrade to v2.7.0 or latest and use SERVER_ENABLED it's written in the readme.

@qdm12 commented on GitHub (Jul 5, 2024): If you're running with Docker just don't publish the port and that's it really. The ui server won't consume any resources really if it's not accessed (and even then, it barely consumes anything). Alternatively, upgrade to v2.7.0 or latest and use `SERVER_ENABLED` it's written in the readme.
saavagebueno commented 2025-11-20 04:23:54 -05:00
Author
Owner
Copy Link

@l4l4l4l4 commented on GitHub (Jul 5, 2024):

Can't do that due to #761

@l4l4l4l4 commented on GitHub (Jul 5, 2024): Can't do that due to #761
saavagebueno commented 2025-11-20 04:23:54 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jul 6, 2024):

You can specify multiple owners with "host" as described in the v2.7.0 readme (future releases will stay retrocompatible too). Or use the latest docker image.

@qdm12 commented on GitHub (Jul 6, 2024): You can specify multiple owners with `"host"` as described in the v2.7.0 readme (future releases will stay retrocompatible too). Or use the latest docker image.
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#418
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?