This message was deleted.

What could be the reason for the following behavior? • Running a semi-automated installation with provisioning scripts and rdctl • When installing for example RD 1.9.1 the installation fails with "Proxy Authentication Required" • Occasionally it is possible to shutdown RD, restart it and RD finishes the installation process successfully. But sometimes the installation does not recover. • seems to be similar with versions > 1.9.1

rdctl start \
 --experimental.virtual-machine.networking-tunnel \
 --kubernetes.options.traefik=false \
 --experimental.virtual-machine.proxy.address <http://my.proxy.org|my.proxy.org> \
 --experimental.virtual-machine.proxy.port 1234 \
 --experimental.virtual-machine.proxy.enabled \
 --kubernetes.version 1.21.14

time="2024-01-03T09:15:44+01:00" level=info msg="About to launch C:\\Program Files\\Rancher Desktop\\Rancher Desktop.exe --kubernetes.version 1.21.14 --kubernetes.options.traefik=false --experimental.virtualMachine.networkingTunnel=true --experimental.virtualMachine.proxy.enabled=true --experimental.virtualMachine.proxy.address <http://my.proxy.org|my.proxy.org> --experimental.virtualMachine.proxy.port 1234 ...\n"
task: "k1:rd:start" finished
theuser@thehost:~/work/project/rd$
(node:14144) UnhandledPromiseRejectionWarning: Error: Could not fetch releases: Proxy Authentication Required
    at tn.updateCache (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:31:100243)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
(Use `Rancher Desktop --trace-warnings ...` to show where the warning was created)
(node:14144) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see <https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode>). (rejection id: 1)
(node:14144) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at <https://desktop.version.rancher.io/v1/checkupgrade> reason: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\node-fetch\lib\index.js:273:32
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async js (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:43:112549)
    at async Ps.checkForUpdates (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:43:113495)
    at async Ps.getLatestVersion (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:43:114991)
    at async Ms.getUpdateInfoAndProvider (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:319:19)
    at async Ms.doCheckForUpdates (C:\Program Files\Rancher Desktop\resources\app.asar\node_modules\electron-updater\out\AppUpdater.js:333:24)
    at async Xs (C:\Program Files\Rancher Desktop\resources\app.asar\dist\app\background.js:43:121824)
(node:14144) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see <https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode>). (rejection id: 3)