#436 Connection failed. Try again later.

Avoinna
1 vuosi sitten avasi iahimoh · 3 kommenttia
iahimoh kommentoitu 1 vuosi sitten

Closest thing I could find was #401 but I'm not on the CN servers. when I open genshin it takes an unusual amount of time before it prompts me to log-in, and when I try logging in any account "Connection failed. Try again later." pops up, no error code. I use arch linux, wine-ge and lutris. I have no idea what could be happening.

Closest thing I could find was #401 but I'm not on the CN servers. when I open genshin it takes an unusual amount of time before it prompts me to log-in, and when I try logging in any account "Connection failed. Try again later." pops up, no error code. I use arch linux, wine-ge and lutris. I have no idea what could be happening.
Krock kommentoitu 1 vuosi sitten
Omistaja

@iahimoh Have you yet checked the corresponding TROUBLESHOOTING.md entry?

Similar reports: #347 (IPv6), #382 (timeout on join)

You could also attempt to ping the *dispatch* domains mentioned in network.md, e.g. dispatchosglobal.yuanshen.com to check whether the important servers are reachable.

@iahimoh Have you yet checked the corresponding [TROUBLESHOOTING.md entry](src/master/TROUBLESHOOTING.md#error-4206-or-connection-timed-out)? Similar reports: #347 (IPv6), #382 (timeout on join) You could also attempt to ping the `*dispatch*` domains mentioned in [network.md](src/master/dev_tools/network.md#2-startup--login), e.g. `dispatchosglobal.yuanshen.com` to check whether the important servers are reachable.
iahimoh kommentoitu 1 vuosi sitten
Tekijä

I tried pinging the dispatch servers, successfully. I have also tried precedence ::ffff:0:0/96 100 in /etc/gai.conf, didn't change much. changing my network fixed the issue once, but doing the same again doesn't fix it anymore.

I tried pinging the dispatch servers, successfully. I have also tried `precedence ::ffff:0:0/96 100` in `/etc/gai.conf`, didn't change much. changing my network fixed the issue once, but doing the same again doesn't fix it anymore.
iahimoh kommentoitu 1 vuosi sitten
Tekijä

My usual network doesn't have ipv6, but the one I changed to and fixed the issue has. Apparently it didn't fixed the issue more than once because the nameservers in /etc/resolv.conf need to be in a specific order, if not the game will throw this error at me. My KDE does a horrible job at keeping track of this file in particular, like, even after removing a DNS from the GUI and removing it from the conf file, KDE will still put it in the conf file. So not only does my game now needs ipv6 (for reasons?!), it also needs KDE to not screw up my files (impossible). I say all of this because I've done some testing, I might be missing something, or something new might pop up and prove me wrong, i think?

My usual network doesn't have ipv6, but the one I changed to and fixed the issue has. Apparently it didn't fixed the issue more than once because the nameservers in /etc/resolv.conf need to be in a specific order, if not the game will throw this error at me. My KDE does a horrible job at keeping track of this file in particular, like, even after removing a DNS from the GUI and removing it from the conf file, KDE will still put it in the conf file. So not only does my game now needs ipv6 (for reasons?!), it also needs KDE to not screw up my files (impossible). I say all of this because I've done some testing, I might be missing something, or something new might pop up and prove me wrong, i think?
Kirjaudu sisään osallistuaksesi tähän keskusteluun.
Ei merkkipaalua
Ei osoitettua
2 osallistujaa
Ladataan...
Peruuta
Tallenna
Sisältöä ei vielä ole.