Hello osu! community:
I use an old WindowsXP computer(I know it's dumb but its my only device) with .NET Framework 4.0 to play osu, but I met problem in installion and login.
Detail:
Though I can access osu! website, I could't use osu!updater. It just stuck in searching the update and said "an error has occured". So I downloaded osu! on a mirror website.(However, the old installer can work normally)
Also, my osu! can't access Bancho, which means I can't login my account.
osu! version 20231102.5(also happens in older versions)
ISP:China Telecom
I use an old WindowsXP computer(I know it's dumb but its my only device) with .NET Framework 4.0 to play osu, but I met problem in installion and login.
Detail:
Though I can access osu! website, I could't use osu!updater. It just stuck in searching the update and said "an error has occured". So I downloaded osu! on a mirror website.(However, the old installer can work normally)
Also, my osu! can't access Bancho, which means I can't login my account.
osu! version 20231102.5(also happens in older versions)
ISP:China Telecom
Measures taken
- I have searched the wiki and community but no satisfied answer was given.
- osu! can access firewall and my anti-virus software.
- network.log was not found in Logs folder.
- tracert results are showed in the next box.
Tracert Results
Tracing route to cho.ppy.sh [162.243.131.91] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1] 2 1 ms 1 ms 1 ms 100.64.48.1 3 4 ms 3 ms * hn.kd.dhcp [61.54.106.221] 4 6 ms 6 ms 3 ms pc189.zz.ha.cn [61.168.31.189] 5 17 ms 18 ms 19 ms 219.158.121.129 6 30 ms 23 ms 23 ms 219.158.7.134 7 25 ms 23 ms 23 ms 219.158.8.190 8 179 ms 175 ms 175 ms 219.158.116.238 9 193 ms 193 ms 193 ms 4.53.209.21 10 * 192 ms * ae2.3605.edge9.SanJose1.level3.net [4.69.219.65] 11 199 ms 198 ms 198 ms 4.7.18.10 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 192 ms 191 ms 191 ms 162.243.131.91 Trace complete.
Tracing route to osu.ppy.sh [172.67.14.100] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1] 2 2 ms 3 ms 2 ms 100.64.48.1 3 * 4 ms * hn.kd.dhcp [61.54.106.221] 4 6 ms 5 ms 4 ms pc145.zz.ha.cn [61.168.38.145] 5 25 ms 24 ms 24 ms 219.158.101.37 6 30 ms 31 ms 32 ms 219.158.7.130 7 30 ms 31 ms 31 ms 219.158.8.190 8 176 ms 183 ms 183 ms 219.158.116.238 9 224 ms 265 ms 284 ms 
.55.148.204.in-addr.arpa [204.148.55.105] 10 * * * Request timed out. 11 * 253 ms 222 ms 
.55.148.204.in-addr.arpa [204.148.55.2] 12 294 ms 230 ms 215 ms 172.68.188.20 13 296 ms 240 ms 211 ms 172.67.14.100 Trace complete.
Tracing route to m1.ppy.sh [162.243.70.14] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 [192.168.1.1] 2 2 ms 1 ms 1 ms 100.64.48.1 3 3 ms 3 ms 3 ms hn.kd.dhcp [61.54.106.213] 4 5 ms 5 ms 6 ms pc201.zz.ha.cn [61.168.37.201] 5 11 ms * * 219.158.100.241 6 15 ms 16 ms 15 ms 219.158.18.70 7 33 ms 31 ms 31 ms 219.158.3.30 8 208 ms 212 ms 219 ms 219.158.16.94 9 195 ms 192 ms 199 ms if-bundle-39.qcore1.lvw-losangeles.as6453.net [2 07.45.219.8] 10 * * * Request timed out. 11 * 261 ms 261 ms if-ae-60-2.tcore1.sv1-santaclara.as6453.net [63.243.250.54] 12 * 243 ms * if-ae-0-3.tcore2.sv1-santaclara.as6453.net [63.243.250.61] 13 267 ms 266 ms * if-ae-18-2.tcore1.sqn-sanjose.as6453.net [63.243.205.72] 14 * 241 ms 241 ms if-ae-36-2.tcore1.nto-newyork.as6453.net [63.243.128.166] 15 264 ms 264 ms 264 ms if-be-9-2.ecore1.n75-newyork.as6453.net [63.243.128.122] 16 240 ms 241 ms 240 ms if-ae-57-2.tcore1.n75-newyork.as6453.net [66.110.96.58] 17 365 ms 363 ms 321 ms 66.110.96.26 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 350 ms 374 ms 352 ms 162.243.70.14 Trace complete.