UNRESOLVED - Springer/Nature Blocked by Client Challenge on Specific Chromium-based Browsers (ungoogled-chromium, Doubao)

Problem

Trying to access Springer/Nature webpages result in a periodically-happening error page:

Figure 1: Client challenge error screen.

which occurred on ungoogled-chromium and Doubao browser. On Microsoft Edge(same computer) and via(Android mobile) in the same network environment, it didn’t occur.

Something Already Tried

• Privileges in chrome://settings: not shown for nature.com. However, support.springernature.com is accessible.
• VPN: not effective.
• Changing network situation(WIFI connection): not effective. I tried to use cellular connection from my cellphone on my computer, which didn’t change anything.
• Deleting all cached data, cookies, etc.: not effective.
• Anonymous mode (without any extensions): not effective.
• Directly disabling all extensions: not effective.
• Disabling WebGL and Spoof WebGL Info: not effective.
• Directly executed from command line, without any additional arguments: not effective.
• Completely restarting the computer: not effective.
• Changing to other browsers:
  • Integrated browser in VSCode: working fine. It’s also based on chrome, but chrome://settings is not accessible.
  • Chrome: not effective.
  • Firefox: working fine.
• Starting the browser from command line, with loggings on (chrome.exe --enable-logging=stderr -v=0):

[19328:10256:0615/204312.869:ERROR:net\cert\ev_root_ca_metadata.cc:161] Failed to decode OID: 0
[19328:10140:0615/204313.129:INFO:CONSOLE:74] "Script load error event: [object Event]", source: https://www.nature.com/ (74)
[19328:10140:0615/204313.129:INFO:CONSOLE:78] "Error: Failed to load script: https://www.nature.com/_fs-ch-1T1wmsGaOgGaSxcX/script.js?reload=true. Please contact the service administrator.", source: https://www.nature.com/ (78)

• Disabling Reduced System Info and Remove Client Hints: not effective.
• Changing User Agent to Firefox by using User-Agent Switcher: not effective.

Update on 2026-06-16

JA GREAT NOW IT WORKS IDK HOW THO XDDDDD I GUESS ITS JUST SERVER’S FAULT