Replies: 13 comments 1 reply
-
Check the config.json file is bind mounted correctly? It seems it doesn't find it (so it creates it as empty) |
Beta Was this translation helpful? Give feedback.
-
It created an empty file which I later filled. How do I verify if bind is mounted? I followed each step. |
Beta Was this translation helpful? Give feedback.
-
Where is your config.json file on your host system, and what's your bind mount configured for the |
Beta Was this translation helpful? Give feedback.
-
`/mnt/user/appdata/ddns-updater/data` I don’t follow on bind mount - is that the “touch” command? I followed each line from the unraid instructions exactly.
|
Beta Was this translation helpful? Give feedback.
-
You should a volume mount (aka bind mount) between |
Beta Was this translation helpful? Give feedback.
-
Correct. That’s how mine is setup. /updater/data in the container and /mnt/user/appdata/ddns-updater/data is where config is stored.
|
Beta Was this translation helpful? Give feedback.
-
Try running it with |
Beta Was this translation helpful? Give feedback.
-
```
Running version latest built on 2024-02-08T13:09:44.329Z (commit e676983)
🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new
🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new
✨ New feature? https://github.com/qdm12/ddns-updater/issues/new
☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new
💻 Email? ***@***.***
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2024-02-08T17:05:31Z INFO Settings summary:
├── HTTP client
| └── Timeout: 10s
├── Update
| ├── Period: 5m0s
| └── Cooldown: 5m0s
├── Public IP fetching
| ├── HTTP enabled: yes
| ├── HTTP IP providers
| | └── all
| ├── HTTP IPv4 providers
| | └── all
| ├── HTTP IPv6 providers
| | └── all
| ├── DNS enabled: yes
| ├── DNS timeout: 3s
| └── 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
├── Backup: disabled
└── Logger
├── Level: debug
└── Caller: hidden
2024-02-08T17:05:31Z INFO reading JSON config from file /updater/data/config.json
2024-02-08T17:05:31Z DEBUG config read: {}
2024-02-08T17:05:31Z WARN Found no setting to update record
2024-02-08T17:05:32Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: false
2024-02-08T17:05:32Z INFO [healthcheck server] listening on 127.0.0.1:9999
2024-02-08T17:05:32Z INFO [backup] disabled
2024-02-08T17:05:32Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: invalid IP, v6: invalid IP
2024-02-08T17:05:32Z INFO [http server] listening on :8000
2024/02/08 17:06:06 "GET http://192.168.1.100:8000/ HTTP/1.1" from 192.168.3.3:64069 - 200 1273B in 17.391µs
2024/02/08 17:06:06 "GET http://192.168.1.100:8000/favicon.ico HTTP/1.1" from 192.168.3.3:64069 - 404 19B in 6.801µs
```
|
Beta Was this translation helpful? Give feedback.
-
Yes it doesn't find the file
so it creates as an empty json object Try accessing a terminal on your Unraid machine and run docker inspect --format "{{json .Mounts}}" $(docker ps --filter "label=org.opencontainers.image.title=ddns-updater" --latest --format "{{.ID}}" --no-trunc) That should print out the bind mounts |
Beta Was this translation helpful? Give feedback.
-
Copy/pasted and here was the response: |
Beta Was this translation helpful? Give feedback.
-
Looks like it’s my config file that gets printed out.
… On Feb 14, 2024, at 01:22, Quentin McGaw ***@***.***> wrote:
cat /mnt/user/appdata/ddns-updater/data/config.json
|
Beta Was this translation helpful? Give feedback.
-
Sorry last resort would be to set your entire json config in the |
Beta Was this translation helpful? Give feedback.
-
I had a similar issue in the Docker on Unraid in that in my case the json was being read (from /mnt/user/appdata/ddns-updater and not from /mnt/user/appdata/ddns-updater/data), but it was not updating Freedns (note the token is not the one in the main DDNS page!). I had edited the json in Windows using Notpead++ through Winscp. This appeared to mess up file permissions a bit. But I put them straight. Still no joy. I then manually edited the 'Container Path: /updater/data' to be '/mnt/user/appdata/ddns-updater/data' and a copied the json to the data directory and then applied the chnage to the docker. The docker was updated and after that the updater worked fine with Freedns. Result. I suspect it's a permissions/cache issue, but that's just a wild guess! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
TLDR: Describe your issue in a one liner here
I've set up the config.json several times and it wont update when I check the webui.
I recently rebuilt a corrupt docker.img and it was working perfectly before.
Is this urgent: No
DNS provider(s) you use: Cloudflare
Program version:
Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)
What are you using to run the container: unraid
Extra information (optional)
Logs:
Host OS:
Unraid
Beta Was this translation helpful? Give feedback.
All reactions