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

Closed
opened 1 month ago by anlorsp · 3 comments
anlorsp commented 1 month ago

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 1 month ago
Owner

@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 1 month ago
Poster

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.
Krock commented 10 hours ago
Owner

Script updated as of 0d9dd1e4c.

The nmcli (or equivalent) workaround is generally needed on all platforms for a while, thus allowing dispatchcnglobal again does in fact make it more consistent.

Assuming the issue is addressed sufficiently. If not: please leave a comment here and reopen the issue (if possible).

Script updated as of 0d9dd1e4c. The `nmcli` (or equivalent) workaround is generally needed on all platforms for a while, thus allowing `dispatchcnglobal` again does in fact make it more consistent. Assuming the issue is addressed sufficiently. If not: please leave a comment here and reopen the issue (if possible).
Sign in to join this conversation.
Loading...
Cancel
Save
There is no content yet.