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

Error: error decoding response body: missing field locked at line 1 column 433 #61

Open
domtoro opened this issue Jul 28, 2024 · 3 comments · May be fixed by #63
Open

Error: error decoding response body: missing field locked at line 1 column 433 #61

domtoro opened this issue Jul 28, 2024 · 3 comments · May be fixed by #63

Comments

@domtoro
Copy link

domtoro commented Jul 28, 2024

I've encountered a new issue with cfdyndns. It began before the most recent log rotation, so I'm unsure of the exact time when the problem started.

Jul 28 15:40:01 somehostname systemd[1]: Started CloudFlare Dynamic DNS Client.
Jul 28 15:40:01 somehostname cfdyndns-start[202436]:  INFO  cfdyndns::ip > XXX.YYY.ZZZ.115
Jul 28 15:40:01 somehostname cfdyndns-start[202436]:  INFO  cfdyndns::ip > 2001:AAAA:BBBB:CCCC:DDDD:EEEE:FFFF:FFFF
Jul 28 15:40:07 somehostname cfdyndns-start[202436]: Error: error decoding response body: missing field `locked` at line 1 column 433
Jul 28 15:40:07 somehostname systemd[1]: cfdyndns.service: Main process exited, code=exited, status=1/FAILURE

I am using cfdyndns v 0.2.1 on NixOS 24.05.

@anthr76
Copy link

anthr76 commented Aug 18, 2024

I'm seeing this as well

@JosephGoulden
Copy link

We need this merged PR, now waiting for a release of cloudflare-rs.

@Pablo1107
Copy link

Currently we are not using upstream cloudflare-rs but this fork from @Wyn-Price

Please rebase your fork with upstream master and update the dependency here.

@Pablo1107 Pablo1107 linked a pull request Oct 21, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

4 participants