WSL1 chromium under chromedriver returns empty body because of net::ERR_FAILED

Microsoft Windows [Version 10.0.19044.1147]
Kernel version: 5.10.16
Debian 10

lunching chrome with

/usr/bin/chromium --allow-insecure-localhost --allow-running-insecure-content --debug --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-gpu --disable-hang-monitor --disable-ipv6 --disable-popup-blocking --disable-prompt-on-repost --disable-sync --enable-automation --enable-blink-features=ShadowDOMV0 --enable-logging --headless --ignore-certificate-errors --log-level=0 --no-first-run --no-sandbox --no-service-autorun --password-store=basic --remote-debugging-port=9222 --test-type=webdriver --use-mock-keychain --user-data-dir=/tmp/.org.chromium.Chromium.YrhI4h --window-size=1024,768

chromedriver show this log

[1627297446,877][DEBUG]: DevTools WebSocket Event: DOM.childNodeInserted 6C7292B58B8BC0F325D2AB63FC819E17 {
   "node": {
      "attributes": [ "lang", "ru" ],
      "backendNodeId": 3,
      "childNodeCount": 0,
      "frameId": "6C7292B58B8BC0F325D2AB63FC819E17",
      "localName": "html",
      "nodeId": 3,
      "nodeName": "HTML",
      "nodeType": 1,
      "nodeValue": ""
   },
   "parentNodeId": 1,
   "previousNodeId": 2
}
[1627297446,877][DEBUG]: DevTools WebSocket Event: DOM.childNodeCountUpdated 6C7292B58B8BC0F325D2AB63FC819E17 {
   "childNodeCount": 1,
   "nodeId": 3
}
[1627297446,877][DEBUG]: DevTools WebSocket Event: Log.entryAdded 6C7292B58B8BC0F325D2AB63FC819E17 {
   "entry": {
      "level": "error",
      "networkRequestId": "8090E523E14B538F152D38640D86B8C8",
      "source": "network",
      "text": "Failed to load resource: net::ERR_FAILED",
      "timestamp": 1.6272974468764902e+12,
      "url": "https://hybrid.kz/registration/"
   }
}

Chrome headless remote debugger has only one entry in console
Failed to load resource: net::ERR_FAILED

and loaded HTML page with HEAD tag only.

Under WSL2 everything works as expected

Reproduce the failure with the reported Chromium command on WSL1 using Debian 10 and compare it with WSL2, checking the shown remote-debugger output and the affected URL. Identify whether the empty document and net::ERR_FAILED originate in WSL1 networking or the Chromium setup; done means the page loads its body successfully under WSL1.