-
Notifications
You must be signed in to change notification settings - Fork 23
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
The latest version (5b53751) is unable to use TOTP. #200
Comments
Just to add, I'm using this method to run Docker: |
Did you try rerun it? When you login on your NOIP account through the browser does the dashboard page loads right after you login? |
I've tried using two sets of accounts separately, each for four attempts, and the results are the same. Now, when I use the previous version, everything works fine. |
Additionally, I've found that running the latest version using the command |
However, since I need to automate the scheduling, I prefer using the method |
hello there, I then activate the 2FA in noip.com and saved the key. now, I modify my script to match the command line including the NO_IP_TOTP_KEY but I'm still stuck at "Could not login. Check if account is blocked." any idea? |
Same here! Running it from command line in a synology NAS with the following command: docker run --rm -it --shm-size=2g --env NO_IP_USERNAME=xxxxx --env NO_IP_PASSWORD=xxxxx --env NO_IP_TOTP_KEY=xxxxxxx simaofsilva/noip-renewer |
me too,display: I use browser can login and update ddns name。 |
@simao-silva |
For me it's still not working. I've cloned the repo and build locally. Using the docker run --rm -it simaofsilva/noip-renewer |
The login page for noip has been redesigned again... |
The new issue now is: |
@simao-silva |
@johngianni |
this is working fine ! thank you! |
the update makes it running fine, thank you |
Hi, im still getting account blocked...
|
When attempting to use TOTP with the latest version (5b53751), it times out and displays "Could not login. Check if account is blocked.". However, TOTP works fine with the previous version (bfdfa01).
The text was updated successfully, but these errors were encountered: