-
Notifications
You must be signed in to change notification settings - Fork 767
dns/ddclient: Treat 204 response as successful #3618
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
Conversation
|
yeah, 2xx range should indicate ok. that would have been my comment as well :) |
|
@AdSchellevis Just got the update to 1.16.1 on my home router and still it complains about a 204 response ( |
|
Will be released in 23.7.8. |
|
So it wont work in <23.7.8 even though it says that 1.16_1 is installed and the changelog mentions the fix for this? |
|
You are right, it’s already in 23.7.7. Native backend? Dyndns2? |
|
Native backend and custom service with 'Custom GET'. My understanding is that that should go through the same code as dyndns2. |
|
I would expect so, yes, looking at the code on my end, it seems to include the adjusted line: |
|
Old daemon still running? |
|
I also have the expected code in place and tried restarting the daemon but still no luck, getting the same error. |
|
@sudnam ok, something is off with my code, I'll take a look |
|
Right, I totally missed that as well... Is there an easy way to test out that commit in a running system? Without compiling a package and stuff yourself. |
|
|
@fichtner Perfect, thanks! @AdSchellevis Now I'm getting a |
|
no clue, you probably have to debug further, nothing else has changed here. the most likely crash point is
There's a notice message earlier |
|
Right, that should be it. Since the response is 204, I'll have a look at a fix later tonight. |
|
ok, here you go 85e4a25 |
|
Thank you very much for all the help! |
Treat a 204 response code as successful when using the dyndns2 provider. Should help with #3585 (by using the custom provider) until we get a proper provider for domeneshop.