Crashing language server (terraform-ls)

After an update to the latest version (v2.12.1) my Terraform language server does not work anymore. As a consequence, I do not have auto-completion like I used to just over a week ago. Also, the following error message appears:

The Language Server: 
file:///<path-pointing-to-my-terraform-project> server crashed 5 times in the last 3 minutes. 
The server will not be restarted.

These are the VSCode settings I specified in the settings.json file:

...
"terraform.languageServer": {
        "external": true,
        "pathToBinary": "C:\\Portable\\terraform\\terraform.exe",
        "args": [
            "serve"
        ],
        "maxNumberOfProblems": 100,
        "trace.server": "off"
    },
...

Is it normal that the path displayed in the error message and the one I set in the settings.json file are different? Can you help me troubleshoot the error?

I’m using a Win10 x64 workstation.

[radeksimko]

I have created https://github.com/hashicorp/vscode-terraform/issues/667 to address the proxy related issues.

terraform-ls is its own thing, separate from terraform binary

The field is under terraform.languageServer section and the description already mentions this, so I’m not sure what more can be done in this area? 🤔

https://github.com/hashicorp/vscode-terraform/blob/ab57089375e2c5f989bf854ca47e45335e3ac1d6/package.json#L101

[radeksimko]

I’m starting to think that terraform.exe and terraform-ls are two different things.

Yes - these are two different things. We do not bundle the language server with Terraform itself, at least not at this point.

No need to apologize - I’m just curious what motived you to set this config option? The extension should just install the LS automatically after first activation and it should not need any manual configuration at all.

Is there any piece of documentation that needs updating, or adding somewhere?

I tried to re-install the extension without specifying the path but I get this error:

I’m assuming that’s the (unfortunately vague) message from a popup. I haven’t quite figured out where that one comes from and how to make it more useful, but I’ve seen it before.

I wonder if this could be related to the way you run VS Code or the network you’re on?

Generally the extension needs to:

• be able to reach releases.hashicorp.com - if you’re behind any kind of restrictive corporate firewall that blocks requests to that domain then I imagine that might confuse the updater.
• be able to create a new lsp directory within the extension dir (i.e. $HOME/.vscode/extensions/hashicorp.terraform-2.12.1) and be able to write files into that directory