tickets #54182
closedUnable to login to Opensuse forum
0%
Description
Hi, I'm trying to log into the opensuse forum (ironically to report a bug) but I can't log-in. Any browser I use gets stuck in an infinite TLS-handshake loop during log-in. I was told to report this issue to you.
Many thanks,
Andy.
Updated by okurz over 5 years ago
- Related to tickets #42599: [admin] Redirection limit for this URL exceeded trying to reach BOO and forums added
Updated by okurz over 5 years ago
- Related to tickets #50681: Cannot login to progress.opensuse.org added
Updated by okurz about 5 years ago
- Category set to Servers hosted in Provo
- Status changed from New to Feedback
- Assignee set to okurz
I just closed ticket https://progress.opensuse.org/issues/42599 #42599 . Do you still see this issue?
Updated by andy_millman@yahoo.co.uk about 5 years ago
HI yes I am still experiencing this bug.Unable to log in to opensuse forums.
Andy.
Updated by okurz about 5 years ago
I see. Thank you for letting me know. Then it looks like a problem specific to your account. Can you please report the issue over https://rio.microfocuscloud.com ? I hope this is available for you with the SUSE account you have. If you are unable to do so I can create the ticket myself but this would be less efficient for me to act as middle-man :)
Updated by andy_millman@yahoo.co.uk about 5 years ago
Hi, many thanks for the reply. Unfortunately my opensuse account won't let me log in to that domain.
Updated by okurz about 5 years ago
Well, the best I myself can do is create a RIO ticket myself and forward all information. Can you help to answer the following questions upfront:
- which browser(s) do you use, on which operating system, which version (as you mentioned "any browser you use" reproduces this)?
- are other services also affected, e.g. bugzilla.opensuse.org, connect.opensuse.org, progress.opensuse.org, build.opensuse.org ? They should all work with the same account
- did you crosscheck another account, another browser, different OS?
For making you searchable in the logs, the following additional information is probably helpful:
- your IP at the time of failure
- the exact date and time of the failure (including timezone)
- the URL you (attempted to) use
It might also be helpful to know when you logged in - ideally with the exact time