forum

[Archived] Can't log in to osu! after installing a new OS (Windows 10)

posted
Total Posts
1
Topic Starter
Hypocritical_old_1
Below is my tracert log of the 3 hosts to osu. I can't log in to my account on osu!, which is BiggieBeese, after installing Windows 10. I've followed ALL of the troubleshooting tips and none of them have worked. I am entering my user and password normally as I can enter the website just fine. I will also include the network.log and the results from that below.

6/1/2018 3:40:20 PM: ----------------------------------------------------------
6/1/2018 3:40:20 PM: Network Log for Oofster
6/1/2018 3:40:20 PM: osu! version unknown
6/1/2018 3:40:20 PM: Running on Microsoft Windows NT 6.3.9600.0, 12 cores
6/1/2018 3:40:20 PM: ----------------------------------------------------------
6/1/2018 3:40:20 PM: Request to https://osu.ppy.sh/web/check-updates.php?action=check&stream=beta40&time=636634500201680490 () successfully completed!
6/1/2018 3:40:45 PM: Request to https://osu.ppy.sh/web/bancho_connect.php?v=b20180510.3beta&u=alfredobakos4@gmail.com&h=********************************&fx=dotnet30|dotnet35|dotnet4|dotnet4|dotnet4&ch=96c35736d80675cb248b5b69bacad2a1:309C2304F26C..00000000000000E0.:3700284a6a17447d335494987ce3faad:0ad04a55983dd914da828a360b3bf504:ba3f163a6146ce7420924396faade2c7:&retry=0 () successfully completed!
6/1/2018 3:40:45 PM: Request to https://c.ppy.sh () successfully completed!



Then, the tracert is after the line shown below:

------------------------------------------------------------------------------------------------------------------------------------


Microsoft Windows [Version 10.0.16299.461]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Oofster>tracert cho.ppy.sh\
Unable to resolve target system name cho.ppy.sh\.

C:\Users\Oofster>tracert cho.ppy.sh

Tracing route to cho.ppy.sh [162.243.131.91]
over a maximum of 30 hops:

1 1 ms 4 ms 5 ms 10.0.0.1
2 13 ms 14 ms 14 ms 96.120.97.17
3 12 ms 14 ms 14 ms xe-0-2-1-sur02.boynton.fl.pompano.comcast.net [68.85.126.217]
4 19 ms 14 ms 19 ms 68.85.127.121
5 19 ms 26 ms 22 ms be-40-ar01.northdade.fl.pompano.comcast.net [68.86.165.161]
6 24 ms 19 ms 19 ms be-20214-cr02.miami.fl.ibone.comcast.net [68.86.90.205]
7 25 ms 20 ms 20 ms be-12274-pe01.nota.fl.ibone.comcast.net [68.86.82.154]
8 18 ms 24 ms 19 ms 50.242.151.66
9 106 ms 100 ms 99 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
10 24 ms 29 ms 19 ms ae-8.r20.miamfl02.us.bb.gin.ntt.net [129.250.3.149]
11 41 ms 49 ms 45 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
12 101 ms 108 ms 104 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
13 106 ms 106 ms 104 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 103 ms 107 ms 104 ms ae-4.r05.plalca01.us.bb.gin.ntt.net [129.250.5.32]
15 * * * Request timed out.
16 * * * Request timed out.
17 109 ms 109 ms 101 ms 162.243.131.91

Trace complete.

C:\Users\Oofster>tracert osu.ppy.sh

Tracing route to osu.ppy.sh [2400:cb00:2048:1::6814:341c]
over a maximum of 30 hops:

1 5 ms 4 ms 4 ms 2601:580:4400:5988:68ee:96ff:fecd:873a
2 13 ms 14 ms 14 ms 2001:558:40c0:3c::1
3 11 ms 14 ms 14 ms xe-0-2-2-sur02.boynton.fl.pompano.comcast.net [2001:558:72:102::1]
4 12 ms 18 ms 14 ms 2001:558:70:3fe::1
5 16 ms 21 ms 18 ms 2001:558:70:409::1
6 20 ms * * be-20214-cr02.miami.fl.ibone.comcast.net [2001:558:0:f6b3::1]
7 19 ms 20 ms 21 ms be-12274-pe01.nota.fl.ibone.comcast.net [2001:558:0:f8a6::2]
8 25 ms 16 ms 16 ms 2001:559::dea
9 23 ms 21 ms 16 ms 2400:cb00:2048:1::6814:341c

Trace complete.

C:\Users\Oofster>tracert m1.ppy.sh

Tracing route to m1.ppy.sh [162.243.70.14]
over a maximum of 30 hops:

1 5 ms 3 ms 4 ms 10.0.0.1
2 13 ms 13 ms 10 ms 96.120.97.17
3 11 ms 9 ms 16 ms xe-0-3-1-sur01.boynton.fl.pompano.comcast.net [68.85.126.197]
4 12 ms 14 ms 12 ms 69.139.180.170
5 15 ms 11 ms 17 ms 68.85.127.121
6 17 ms 19 ms 15 ms be-40-ar01.northdade.fl.pompano.comcast.net [68.86.165.161]
7 20 ms 19 ms 19 ms ae13.edge2.Miami1.Level3.net [4.68.62.149]
8 96 ms 94 ms 99 ms ae-2-3602.ear4.Newark1.Level3.net [4.69.211.181]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 82 ms 81 ms 84 ms 162.243.70.14

Trace complete.



Screenshot of network.log: https://prnt.sc/jpqubo
Please sign in to reply.

New reply