mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-21 17:20:36 -05:00
[GH-ISSUE #1412] TOPT don't work correctly #1898
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#1898
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vk2r on GitHub (Sep 4, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1412
I have installed the new version of Pangolin and tried to add a two-factor authentication with QR.
Unfortunately, when adding it to the Ente Auth application, the generated key is incorrect, preventing me from adding TOPT.
Specifications
@oschwartz10612 commented on GitHub (Sep 4, 2025):
I just tested on the latest version and I think it is working? This can
break if the time of your server is off. Could you make sure the time is
right?
I am not super familiar with Ente, but sometimes the string it gives you
is not parsed correctly from pangolin. For example:
otpauth://totp/Pangolin:admin%40fosrl.io?secret=QHNSPVT4LR3JFT62XZWCP7H5GE4ZY2OH&issuer=Pangolin
The actual OTP secret here is QHNSPVT4LR3JFT62XZWCP7H5GE4ZY2OH.
Does that help?
@vk2r commented on GitHub (Sep 5, 2025):
I'm sorry. There was no way.
I tried Microsoft Authenticator and it didn't work either. I tried entering it manually and the same message keeps appearing.
This is my referral URL:
otpauth://totp/Pangolin:admin%40vk-studios.net?secret=COU7NDUXYB3SW2FHTXRPZBFNM222CHBI&issuer=Pangolin
This is the message I get :
It could be due to the time zone mismatch. My VPS is located in Germany and I am in Chile.
How can I change the time zone?
@v1rusnl commented on GitHub (Sep 8, 2025):
sudo dpkg-reconfigure tzdataIf your VPS is Ubuntu or Debian.
Also you can try to pass TZ variable to the Pangolin container using environment variable depending on where you live.
or
@github-actions[bot] commented on GitHub (Sep 23, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@l3pr-org commented on GitHub (Oct 6, 2025):
Looks like OP reacted to the last comment as if their issue was resolved?
@vk2r Do you mind closing the issue if your problem has been fixed?
@vk2r commented on GitHub (Oct 6, 2025):
Close this issue. I reinstalled everything from scratch and it worked without problems.
@l3pr-org commented on GitHub (Oct 16, 2025):
You will have to close the issue yourself. Only the issue creator and repository maintainers/owners have permissions to close issues. There is a 'close issue' button next to the green 'comment' button.