-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Not working on USG 3P #8
Comments
I am using commit 443ad14 with my ER4 because it doesn't require any of the extra parameters in the URL. I'm not really sure why that changed. |
Looking at #6 I think the newer devices use inadyn as their dynamic DNS client, while the USG 3P and a bunch of other devices use ddclient. At a guess it sounds like the two of them are not exactly interchangeable. @willswire what is your take? The way I see it there are two options for this project:
|
@dhutchison perhaps making the worker compatible for both clients is best. I'd be happy to peer-review and help edit some code if you want to make a PR. |
For example the USG-3P
I've created PR #11 if you want to take a look. I've tested it with the device I have, but I could do with someone testing it still works on a UDM still. I've deliberately not updated the readme to say the hosted version supports it just now, I'll leave that for you if you choose to deploy this version. |
It is working awesome. Thank you :D |
feat: added support for ddclient based devices #8
I'm not sure if the USG 3P is different from the UDM in protocol version, and if this is related/caused by #6 or #1.
From a bit of troubleshooting, it appears configuring the Server entry as in the docs that the request to the worker has the following:
(Domain & IP replaced)
From a guess it looks like the USG doesn't support using a custom path on the URL.
Have I setup something wrong or is there a version difference somewhere?
The text was updated successfully, but these errors were encountered: