Generated per edit 3, retrieved from the verbose logs.
This appears to be some weirdness like others have experienced in the following threads:
Plugin download fails - SonarQube - Sonar Community (sonarsource.com)
Scanner always timeout during plugin download - SonarQube - Sonar Community (sonarsource.com)
We’re running SonarQube on AKS with an nginx reverse proxy, utilizing the official helm chart and with the built-in ingress from that chart. Trying to retrieve plugins even from a normal browser has the same behavior where the download “completed” (XXMB downloaded of XXMB) but the connection takes an extremely long time to actually close, and thus the browser to consider it to be actually completed.
We haven’t experienced this with any other AKS-nginx hosted services that deal with files, so this appears to be something peculiar to SonarQube itself. We managed to “solve” this by upping the sonar.ws.timeout variable to 180 seconds as well as slip-streaming any plugins failing to be downloaded into the destination cache location manually.