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

Login button has changed. Please contact support. #30

Closed
BlaydeRunner08 opened this issue Apr 25, 2023 · 6 comments
Closed

Login button has changed. Please contact support. #30

BlaydeRunner08 opened this issue Apr 25, 2023 · 6 comments

Comments

@BlaydeRunner08
Copy link

BlaydeRunner08 commented Apr 25, 2023

Running from a Synology NAS, receive the following:

Opening browser
Login button has changed. Please contact support.

I've tried multiple times on multiple days, with no luck.

This is the same issue as #27 , but that one was closed by accident it seems.

I have a full linux vm that is running https://github.com/loblab/noip-renew, that seems to still be working properly.

@simao-silva
Copy link
Owner

Hi,

I have tested both latest debian and alpine variants and both ran successfully.
That error can also occur if, for example, NOIP requires you to complete a captcha or you have NOIP set to another language that is not English. Is any of this your case? Have you tried access your NOIP account page and log in only using your username and password?

@BlaydeRunner08
Copy link
Author

I quickly popped it onto a test Ubuntu VM, and it worked perfectly, but for some reason, i can't get it to run properly on my Synology... what am I missing here?

@BlaydeRunner08
Copy link
Author

I ssh'd into the NAS and ran the exact same command that ran perfectly on my ubuntu VM, and it gave me the same error as before...

@simao-silva
Copy link
Owner

Unfortunately, I don't know what it could be and I am unable to reproduce this. I will close this until further new developments.

@cfr2305
Copy link

cfr2305 commented Aug 27, 2023

Hi, just because I was facing the same issue on my Synology... In my case the problem was the Pi-hole.

@BlaydeRunner08
Copy link
Author

Thanks @cfr2305, disabling pi-hole allowed the script to run successfully!

have you narrowed down exactly what domain it can't reach that's causing it to fail? On my pihole, I see it requesting:

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

3 participants