Thanks for reporting, looks like another issue we need to fix, that should be fairly easy I think. Will take a look!

I've been encountering this issue with multiple colleagues since version 1.30.0 and with version 1.34.0 the issue is back.

Here are my user settings:

"metals.mavenScript": "/usr/bin/mvn",
"metals.sbtScript": "/opt/sbt/bin/sbt",
"metals.javaHome": "/opt/jdk",
"metals.scalafmtConfigPath": "/home/user/.scalafmt.conf",
"metals.scalafixConfigPath": "/home/user/.scalafix.conf",
"metals.ammoniteJvmProperties": [
    "-Dhttps.proxyHost=127.0.0.1",
    "-Dhttps.proxyPort=3128"
],
"metals.bloopJvmProperties": [
    "-Dhttps.proxyHost=127.0.0.1",
    "-Dhttps.proxyPort=3128"
],
"metals.serverProperties": [
    "-Xmx2G",
    "-Dhttps.proxyHost=127.0.0.1",
    "-Dhttps.proxyPort=3128",
    "-Djavax.net.ssl.trustStore=/home/user/.m2/grobCaTrustStore.jks",
    "-Djavax.net.ssl.trustStorePassword=changeit"
],
"metals.customRepositories": [
    "https://nexuss/nexus/repository/public/"
],
"metals.coursierMirror": "https://nexuss/nexus/repository/public/",

I have removed any additional environment variables (e.g. JAVA_OPTS) and specific settings (e.g. ~/.bloop/bloop.json and ~/.config/coursier/mirror.properties) except ~/.config/coursier/credentials.properties

I've just been running multiple tests removing ~/.cache/coursier/ each time. Things are working with version 1.29.0, 1.32.0 and 1.33.0 (see attached files).
Versions 1.30.0, 1.31.0 and 1.34.0 ignore the server settings and the installation fails (see attached files).

There are two anomalies with the working versions, as well: Bloop fails to start initially, requiring an explicit 'Import build'. That leads to more dependencies being downloaded. That works, as the build server starts afterwards and metals is fully working. However, the download of the bloop dependencies gets reported as ERROR.

One more oddity: I have to specify -Djavax.net.ssl.trustStore for coursier even though the CA certificate has been added to /opt/jdk and any other build tool (maven and sbt) uses the certificte from there...

metals_log_1.29.0.txt
metals_log_1.30.0.txt
metals_log_1.31.0.txt
metals_log_1.32.0.txt
metals_log_1_33_0.txt
metals_log_1.34_0.txt

Edit: Grammar.

@LeUser111 The fix in #1498 was released in v1.32.0 and reverted in v1.34.0, which explains the changes you're seeing.

@tgodzik Why did it need to be reverted? I can submit a modified PR if needed.

The extension on windows stopped working at all so I had to revert some of the changes for now. I plan to get back to it as soon as I can

Looks like we can't add the properties on windows in coursier. Adding back the changes aside from that in #1510

I will double check if it works and then will release new version

This should be now fixed, any chance anyone can confirm? You would need to switch to a prerelease version.

I will also want to check if everything works correctly on windows before doing the release.