#490 Blocking dispatchcnglobal.yuanshen.com leads to 4201 error

開啟中
anlorsp2 天之前創建 · 2 條評論
anlorsp commented 2 天之前

As discussed in #471, blocking dispatchcnglobal.yuanshen.com used to be a workaround for the bilibili start up issue. However, after 5.2 update today, this blocking leads to 4201 'network error' in bilibili version. As for now, unblocking the domain can solve the problem. I don't know whether #471 will reappear later though.

As discussed in #471, blocking `dispatchcnglobal.yuanshen.com` used to be a workaround for the bilibili start up issue. However, after 5.2 update today, this blocking leads to 4201 'network error' in bilibili version. As for now, unblocking the domain can solve the problem. I don't know whether #471 will reappear later though.
Krock commented 2 天之前
所有者

@anlorsp You could as well try the timed nmcli workaround that is documented in TROUBLESHOOTING.md. It is currently used on OSRel to avoid receiving a file upon game start that causes a severe performance issue under Linux.

I will update the document as soon the situation has stabilized in the next few days.

EDIT: 4201 means that the "game server list" server could not be reached. It is mandatory for OSRel, and apparently now too for CNRel.

@anlorsp You could as well try the timed `nmcli` workaround that is documented in `TROUBLESHOOTING.md`. It is currently used on OSRel to avoid receiving a file upon game start that causes a severe performance issue under Linux. I will update the document as soon the situation has stabilized in the next few days. EDIT: 4201 means that the "game server list" server could not be reached. It is mandatory for OSRel, and apparently now too for CNRel.
anlorsp commented 22 小時之前
發佈者

Just as what I worried about, #471 happens again. The nmcli workaround does work for me.

BTW: I have also tried temporarily blocking the domain by editing hosts file and recovering it a few seconds later, but this doesn't work. Even if the time gap is as short as 1 second, the 4201 error happens.

Just as what I worried about, #471 happens again. The `nmcli` workaround does work for me. BTW: I have also tried temporarily blocking the domain by editing hosts file and recovering it a few seconds later, but this doesn't work. Even if the time gap is as short as 1 second, the 4201 error happens.
Sign in to join this conversation.
未選擇里程碑
未指派成員
2 參與者
正在加載...
取消
保存
尚未有任何內容