I can't login to osu!lazer

[danthesodacan]

I have been trying to login to osu!lazer for a long time but it just keeps saying "Attempting to connect..." until I click "cancel". I had this issue since two updates ago, version 2019.919.0, and I still have the issue right now, version 2019.930.0.

osu!lazer version: 2019.930.0

My logs:
network.log
performance.log
runtime.log

All the logs were when the issue happened.

[bdach]

The network logs show no connection errors. Could you wait longer and see if there are any changes in the UI (like a message, something along the lines of Connection is failing, will attempt to reconnect...), or in the log output (like timeout messages)?

Additionally, are you running any firewall software that could be blocking outgoing requests or incoming responses?

[danthesodacan]

I have been running osu!lazer for about 40 minutes now and still on the login problem, but I will check to see if there are any changes on the UI or the logs. I checked my programs to check if I had any firewall software and I do, but i'm not sure if it would block any outgoing requests or anything like that. I turned the firewall program off and then attempted to login again, but it still shows the same issue.

[bdach]

I see - are you running a network setup that would be considered non-standard (a proxy, or something of the sort)?

There have been similar reports of login hangs (see #4234 for an example), but connection issues are particularly tricky to pin down due to a possible multitude of causes.

[danthesodacan]

Not so sure if this is considered non-standard but I connected a wifi adapter which may act like a proxy of some sort? I also left my computer on for at least 8 hours with no changes in the logs or the UI :/ Also, I did see #4234 and messaged salatine, and he/she said that the issue naturally went away after some updates.

[bdach]

It's incredibly strange that you've seen no new entries in the logs for 8 hours now. I'm honestly unsure how to proceed from here. Inspecting outgoing traffic on your machine or running a debugger in your environment could help, but both aren't exactly simple to do.

[peppy]

If you follow APIAccess through, there is one particular case where errors could be occurring but not reported to the log. It requires very specific conditions:

• Is logged in, or was able to authenticate
• Has valid access token
• Is getting a WebException on trying to do the user retrieval request
• Has an unhandled status code (see the switch statement in handleWebException)

I think this may be what is happening. Possibly something specific to the content of the user's profile page, and potentially an issue at osu-web side.

We probably want to add logging in the case of an unhandled status code.

[peppy]

May be improved via ppy/osu-framework#2938.