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

Updates not working with noip #10

Open
Animal-UK opened this issue Mar 24, 2021 · 12 comments
Open

Updates not working with noip #10

Animal-UK opened this issue Mar 24, 2021 · 12 comments

Comments

@Animal-UK
Copy link

Animal-UK commented Mar 24, 2021

Hi,

my updates are not working with noip, does the below look right?

--header="Authorization: IiRVU0VSOiRQQVNTV09SRCIK" --user-agent="no-ip shell script/1.0 [email protected]" https://username:[email protected]/nic/update?hostname=xxx.ddns.net&myip=xx.xx.xx.xx

Ive obviously hidden the sensitive details, if i copy out the URL and post it in browser then noip is successfully updated.

@theonemule
Copy link
Owner

I haven't seen that happen with mine, but hard to say. I'd start with the authentication. Reverse the base64 encoding on the credentials and see what is in that...

@Animal-UK
Copy link
Author

Sorry what do you mean reverse base64 on the credentials? They are clear text in the logs...

@theonemule
Copy link
Owner

The authentication is sent in the base64 encoding.

@Animal-UK
Copy link
Author

Ah i see, how do i capture that?

@theonemule
Copy link
Owner

Check the log for the Authorization header.

@Animal-UK
Copy link
Author

if you're referring to this "--header="Authorization: IiRVU0VSOiRQQVNTV09SRCIK" then its just "$USER:$PASSWORD"

@MichaelLeeHobbs
Copy link

if it's actually $USER:$PASSWORD and not the actual values then it sounds like you didn't pass them in correctly.

@Animal-UK
Copy link
Author

the values are correctly read in portainer... also the same value are seen in the logs as per first post (copy and paste of log)

only decoding shows: "IiRVU0VSOiRQQVNTV09SRCIK" = "$USER:$PASSWORD"

image

@glewellyn
Copy link

glewellyn commented Apr 28, 2021

I appear to have exactly this same issue when I try to update my DuckDNS record.

--header="Authorization: IiRVU0VSOiRQQVNTV09SRCIK" --user-agent="no-ip shell script/1.0 [email protected]" https://g###@####.com:5######6-9##5-4##9-8##6-4##########[email protected]/v3/update?hostname=t#############1.duckdns.org&myip=12.34.56.78

When I connect to the container with a shell I can see this:
bash-4.4# echo $USER
g###@####.com
bash-4.4# echo $PASSWORD
5######6-9##5-4##9-8##6-4##########9

@Animal-UK
Copy link
Author

looks like there is limited to no support for this project..

@theonemule
Copy link
Owner

theonemule commented Jun 13, 2021

This project had been downloaded literally millions of times. I try to offer support, but if it doesn't work in a specific scenario, short of giving me your credentials, it's hard to say what's wrong. Sorry it's not working for you. I wrote this because I had trouble with other NOIP clients.

@Animal-UK
Copy link
Author

Switched to DDNS Updater

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

No branches or pull requests

4 participants