Logging in to git.vdm.dev requires resetting password every time #938
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#938
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Whenever I try to log-in to https://git.vdm.dev
it tells me that the username or password is not correct.
Each time I have to use the forgot password option, then I reset the password and it works for that session.
This has been happening ever since starting to use the site (afer github).
I have also checked the box to remember this device and that doesn't seem to do anything either.
Hi Chris, what is strange about your experience is that we have many clients and staff using this system everyday, and far as I can tell none of them have this issue.
Let me offer to help you in a live call. So should this issue come-up again please contact me directly on telegram and I will try to help you find out what is the cause of the issue.
What is true, is that our system does not keep you logged in indefinitely, and you will be required to login from time to time.
My apoligies for any inconvenience this transition has caused you, will do all I can to resolve this for you.
This isn't a huge problem, just see a problem and would like to fix it; however, right now I'm back teaching and schedule is a bit strange. It's not worth wasting your time right now if nobody else is having the issue. I'll try to gather more info from this end to help identify the issue better.
Also, I used the 'remember me' option and I get back in every time.
So I'm just going to leave this ticket here (if OK with you) and will update as soon as that 'remember' option expires and see if it has a problem again.
Just had to re-log-in and everything worked fine.
Not sure what was happening, but maybe the 'remember' process helped resolve it.