I cannot to my because of the error. I do not have nor use any VPNs. (I saw in the other post that it might be an issue)

I'm using MacOS.

osu! 2025.118.2-lazer

Please game logs. There's a button to export them in settings.

I couldn't find the option to do so. I'm shocked that it's one of the first buttons in options screen D:

https://we.tl/t-w8G2M9kXia

Well, that's the same old

2025-01-23 18:24:18 [verbose]: Request to https://auth.ppy.sh/updates/get failed with System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
2025-01-23 18:24:18 [verbose]: ---> System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.
2025-01-23 18:24:18 [verbose]: ---> System.Net.Sockets.SocketException (54): Connection reset by peer

again...

Normally I'd say to take it up with your ISP because it doesn't look like much can be done, but because many people from all over the world have been reporting this sort of thing, I'll suggest another avenue, if you're willing to go through with it.

In order to debug what could be going wrong with the connection, you could try getting a packet capture using Wireshark. A decent guide how to do that is here: https://www.howtogeek.com/104278/how-to-use-wireshark-to-capture-filter-and-inspect-packets/

FULL DISCLOSURE: Wireshark is a network debugging tool that relies on capturing all data packets that go through your network interfaces. That means that we WILL see ALL network traffic that happened throughout the duration of the capture in the capture. Because of this, DO NOT post network captures publically as they could potentially reveal sensitive data. If you are uncomfortable with this, then please do not feel pressured to try this. The only reason I ask is that are not many options left to actually diagnose this, as the error messages are vague, can't really be refined any further, and I cannot reproduce these symptoms on any devices or networks that I have access to.

If you decide to try this and get a packet capture, please save the network capture to a .pcapng file and e-mail the resulting file to [email protected].

Hi! I have the excact same error in my authentication log file, as you asked i will run wireshark and export the logs to send here when i am done i will send an email!

Wdboyes wrote: 154v6w

Hi! I have the excact same error in my authentication log file, as you asked i will run wireshark and export the logs to send here when i am done i will send an email!

Hello,

The network dump you provided doesn't align with what we are seeing in your game logs. This could be because the connection is blocked on your end (either by software on your computer or network misconfiguration) or because you're running some kind of tunneling software, which would obscure the captured traffic.

This still helps us in narrowing down the possible causes though, so I have a few things for you to try now. Please try these one at a time, then start the game, and let us know which step fixed it if any.

1. If you can, connect to another network and try again. For example, you can try using mobile tethering instead of your home internet access. Make sure your computer is connected to only one network at a time.
2. Are you using a tunneling software, such as a VPN or Apple Private Relay? If yes, please disable them and try again.
3. Using Safari, go to https://ipv6test.google.com/. If it says "You don't have IPv6", please do the following:
   
   1. Open a terminal window, run ifconfig and netstat -nr. Please send the outputs to [email protected].
   2. Try turning off IPv6. On macOS, run System Settings and navigate to Network > Details > T/IP. Set "Configure IPv6" to "Link-Local Only", and try again.
      Note that you might have to repeat this for each network you're testing with.
      If this doesn't help, feel free to revert it to "Automatically".

If none of that helps, we'll need to gather more troubleshooting information.

1. Using Safari, go to https://auth.ppy.sh/cdn-cgi/trace.
   It should show a bunch of debugging information. You may consider the information sensitive (such as your IP address and your nearest Cloudflare location), but you're welcome to send it to [email protected].
2. Can you open a terminal window, run nslookup auth.ppy.sh and provide us the output? (this isn't private info)
3. With all the troubleshooting steps above applied and IPv6 disabled, please run another packet capture and send the .pcapng file to [email protected] again.

Thanks for your cooperation 🙌

I have tried the 3 steps and am getting the same stuff, i dont have ipv6 according to that link. I will send the new information as a reply to your guyses email

So far, I'm leaning toward some software running on your device blocking the connection such as an antivirus. If you can rule that out, please let us know.

But to completely rule out the IPv6-related theory I have, can you run one last capture selecting *every* available interface in Wireshark using Shift, like so?


Sorry to ask for yet another one, I wasn't aware of the macOS-specific extra interfaces.

Yes, i will send a reply to your last email with the pcapng once i am able to complete it

Very late update but it appears that after a long long time and another report of this we may have an actual cause (probably helped by the fact that I own a Mac now that I can fiddle with...)

These sorts of connection failures seem to be caused by Screen Time settings, especially ones that concern any sort of website filtering (the "Content and Privacy" toggle and then the "Access to Web Content" dropdown in the "App Store, Media, Web, & Games" section below it).

I'd like to ask all s affected to check their content & privacy settings, try disabling the filters, or at least adding exceptions for

https://osu-ppy-sh.cinevost.com
https://:ffff:172.67.14.100
https://:ffff:104.22.74.180
https://:ffff:104.22.75.180

(The last three addresses also point at the website but look weird because they point at the website's IP directly rather than the DNS hostname. You can their legitimacy by running nslookup osu-ppy-sh.cinevost.com. I'm only suggesting specifying them because from my experiments with the content filter it seems that specifying osu-ppy-sh.cinevost.com alone may not resolve the issue, so maybe try them as a last resort.)

Also note that from my testing the filtering appears to be somewhat slow to respond to changes sometimes, so a full re-log (via Cmd-Shift-Q) or a complete system reboot after tinkering with the settings may be a good idea to ensure the changes actually take effect.

Hi, I'm having a similar problem, but all I did was update my osu to the new version and now I have "The SSL connection could not be established, see inner exception"

Yes I know my info it just doesn't work and constantly gives me the error. Again I haven't changed anything except for updating my osu.

Edit: Thank you for all the help, it works now!

@H42K9R given that we do not have literally every shouting at us that the game is broken, I unfortunately have to doubt your premise that all you did was update the game. You may not be aware of something changing, and I would say that’s the more likely outcome.

Please try connecting via another network or VPN if you have access to one and, as above, if on macOS please triple check your screen time settings.

Thanks for the quick reply, unfortunately none of what you've suggested has worked for me. I hope there're other possible ways I can try to fix this. If this helps narrow down anything, yes I'm using macOS.

Edit - I realise I'm using a different to reply, yes I'm the same person.

Ok, thank you, I'll delete the , sorry.

Screen time settings / the built-in macOS network filtering is the only cause we have been able to confirm over multiple hours of investigation as to possibly causing these symptoms. If it’s not that you may need to do some research on your own sorry.

Also why are you using two s to reply? You are aware of the game’s policy on multi ing, I hope?

@H42K9R / @SRQSCAT
Quick info:

Community Rules wrote: 3i6g49

Each player may only have ONE , ever. The first you make during registration is your one and only osu! , from the moment of its creation and forevermore. This is YOU. It is not anyone else — not your brother, your mother, your sister, your friend — it is YOU. Don't share your with anyone else. You don't get to make a new one if you lose access to it. Keep it safe.

Please mail [email protected] about the matter. wiki/en/Rules

spaceman_atlas wrote: 6p3z2f

Very late update but it appears that after a long long time and another report of this we may have an actual cause (probably helped by the fact that I own a Mac now that I can fiddle with...)

These sorts of connection failures seem to be caused by Screen Time settings, especially ones that concern any sort of website filtering (the "Content and Privacy" toggle and then the "Access to Web Content" dropdown in the "App Store, Media, Web, & Games" section below it).

I'd like to ask all s affected to check their content & privacy settings, try disabling the filters, or at least adding exceptions for

https://osu-ppy-sh.cinevost.com
https://:ffff:172.67.14.100
https://:ffff:104.22.74.180
https://:ffff:104.22.75.180

(The last three addresses also point at the website but look weird because they point at the website's IP directly rather than the DNS hostname. You can their legitimacy by running nslookup osu-ppy-sh.cinevost.com. I'm only suggesting specifying them because from my experiments with the content filter it seems that specifying osu-ppy-sh.cinevost.com alone may not resolve the issue, so maybe try them as a last resort.)

Also note that from my testing the filtering appears to be somewhat slow to respond to changes sometimes, so a full re-log (via Cmd-Shift-Q) or a complete system reboot after tinkering with the settings may be a good idea to ensure the changes actually take effect.

I've been having the same SSL connection problem and tried all of this, and nothing worked:C

I've tried on mutable networks, changed firewall settings, and screentime settings, and it still doesn't work.

One thing to note, though, when I put "https://:ffff:172.67.14.100
https://:ffff:104.22.74.180
https://:ffff:104.22.75.180" In screentime, and hit "done" then go back into the window, none of those are there, only https://osu-ppy-sh.cinevost.com. stays. Any advice?

this worked for a bit then stopped working:

1. Try launching with custom DNS (Cloudflare or Google)
Sometimes, local routers hijack DNS or inject filtering, even if nslookup works.

(This is what nslookup said (not that it particularly matters):
Server: 192.168.4.1
Address: 192.168.4.1#53

Non-authoritative answer:
Name: auth.ppy.sh
Address: 104.22.75.180
Name: auth.ppy.sh
Address: 104.22.74.180
Name: auth.ppy.sh
Address: 172.67.14.100
)

2. To switch DNS:
Go to System Settings > Network > Wi-Fi > Details

3. Under DNS, click the + and add:

1.1.1.1
1.0.0.1
(Cloudflare DNS — fast + unfiltered)

4. Hit OK and reboot your Mac (doesn't work unless you restart)

Open osu!lazer and try logging in again


EDIT 1: This may be a result of me doing almost everything said in this thread and then doing this and it working. So it may not just be changing your DNS, which works, it may be a combination of multiple things. It took me a long time ot get it working. I suggest using ChatGPT to work with you through the process of doing things. Just make sure you ask GPT what each command does before it erases all of your OSU files and beatmaps. Good luck, everyone facing the SSL error!

Edit 2: It stopped working again :/

Edit 3: It works if I sign in using a hotspot and then switch to my WiFi and then never close osu! or restart my computer. Idk.
I'm aware that this message is probably not helpful and maybe harmful because it messes with your DNS which could make more issues.