Ruby LSP Server Not Running

Oct 13, 2025 by recoveryshake.com 127 views

Introduction

Are you experiencing issues with connecting to the Ruby LSP server in Visual Studio Code? If you're encountering the error code -32097, you're not alone. This error can be frustrating, especially when you're working on a Ruby project and need to use the Ruby LSP extension for features like code completion, debugging, and more.

In this article, we'll explore the possible causes of the error code -32097 and provide step-by-step solutions to help you resolve the issue.

Understanding the Error Code -32097

The error code -32097 typically indicates that the Ruby LSP server is unable to connect to the client. This can be due to various reasons, such as:

Ruby LSP Server Not Running: The Ruby LSP server might not be running, or it might be running in the background, but not accessible to the client.
Ruby LSP Extension Not Installed or Configured Correctly: The Ruby LSP extension might not be installed or configured correctly, preventing the client from connecting to the server.
Ruby Version or Path Issues: There might be issues with the Ruby version or path, preventing the client from connecting to the server.

Reproduction Steps

To reproduce the issue, follow these steps:

Install Ruby via Homebrew: Install Ruby using Homebrew on your macOS system.
Do Not Install rbenv: Do not install rbenv, as it might cause issues with the Ruby LSP server.
Create a Ruby Project: Create a new Ruby project in a directory.
Open the Project in VS Code: Open the project in VS Code using the code . command.
See Errors: See the error messages in the VS Code output panel.

Code Snippet or Error Message

The error message will look something like this:

2025-03-11 14:16:06.660 [info] (houseconcerts) Running command: `rbenv exec ruby -EUTF-8:UTF-8 '/Users/paul/.vscode/extensions/shopify.ruby-lsp-0.9.7/activation.rb'` in /Users/paul/.dev/houseconcerts using shell: /bin/zsh
2025-03-11 14:16:06.668 [info] (houseconcerts) Running command: `/opt/homebrew/opt/ruby/bin/ruby -EUTF-8:UTF-8 '/Users/paul/.vscode/extensions/shopify.ruby-lsp-0.9.7/activation.rb'` in /Users/paul/.dev/houseconcerts using shell: /bin/zsh
2025-03-11 14:16:06.952 [info] (houseconcerts) /bin/sh: ruby-lsp: command not found

2025-03-11 14:16:06.956 [info] (houseconcerts) [Error - 2:16:06 PM] Server process exited with code 127.
2025-03-11 14:16:06.957 [info] (houseconcerts) [Error - 2:16:06 PM] Server initialization failed.
2025-03-11 14:16:06.957 [info] (houseconcerts)   Message: Pending response rejected since connection got disposed
  Code: -32097 
2025-03-11 14:16:06.957 [info] (houseconcerts) [Error - 2:16:06 PM] Ruby LSP client: couldn't create connection to server.
2025-03-11 14:16:06.957 [info] (houseconcerts)   Message: Pending response rejected since connection got disposed
  Code: -32097 
2025-03-11 14:16:06.957 [error] (houseconcerts) Error starting the server: Pending response rejected since connection got disposed
2025-03-11 14:16:14.197 [info] (houseconcerts) [Error - 2:16:14 PM] Connection to server got closed. Server will not be restarted.

Screen Shots

You can also see the error messages in the VS Code output panel.

Solution 1: Check Ruby LSP Server Status

First, check if the Ruby LSP server is running. You can do this by opening the VS Code terminal and running the following command:

ruby-lsp --status

If the server is not running, start it by running the following command:

ruby-lsp --start

Solution 2: Check Ruby LSP Extension Configuration

Next, check if the Ruby LSP extension is installed and configured correctly. You can do this by opening the VS Code settings and searching for "Ruby LSP". Make sure that the "Ruby LSP" extension is enabled and configured correctly.

Solution 3: Check Ruby Version and Path

Finally, check if there are any issues with the Ruby version or path. You can do this by running the following command in the VS Code terminal:

ruby -v

If the Ruby version is not correct, update it to the latest version. If the Ruby path is not correct, update it to the correct path.

Conclusion

In conclusion, the error code -32097 can be caused by various reasons, including the Ruby LSP server not running, the Ruby LSP extension not installed or configured correctly, or Ruby version or path issues. By following the reproduction steps and checking the Ruby LSP server status, extension configuration, and Ruby version and path, you can resolve the issue and connect to the Ruby LSP server successfully.

Additional Tips

Make sure that you have the latest version of the Ruby LSP extension installed.
Check if there are any conflicts with other extensions that might be causing the issue.
Try restarting the VS Code editor and the Ruby LSP server to see if it resolves the issue.

Q: What is the error code -32097 in VS Code?

A: The error code -32097 in VS Code typically indicates that the Ruby LSP server is unable to connect to the client. This can be due to various reasons, such as the Ruby LSP server not running, the Ruby LSP extension not installed or configured correctly, or Ruby version or path issues.

Q: How do I reproduce the issue?

A: To reproduce the issue, follow these steps:

Install Ruby via Homebrew: Install Ruby using Homebrew on your macOS system.
Do Not Install rbenv: Do not install rbenv, as it might cause issues with the Ruby LSP server.
Create a Ruby Project: Create a new Ruby project in a directory.
Open the Project in VS Code: Open the project in VS Code using the code . command.
See Errors: See the error messages in the VS Code output panel.

Q: What are the possible causes of the error code -32097?

A: The possible causes of the error code -32097 include:

Ruby LSP Server Not Running: The Ruby LSP server might not be running, or it might be running in the background, but not accessible to the client.
Ruby LSP Extension Not Installed or Configured Correctly: The Ruby LSP extension might not be installed or configured correctly, preventing the client from connecting to the server.
Ruby Version or Path Issues: There might be issues with the Ruby version or path, preventing the client from connecting to the server.

Q: How do I check the Ruby LSP server status?

A: To check the Ruby LSP server status, open the VS Code terminal and run the following command:

ruby-lsp --status

If the server is not running, start it by running the following command:

ruby-lsp --start

Q: How do I check the Ruby LSP extension configuration?

A: To check the Ruby LSP extension configuration, open the VS Code settings and search for "Ruby LSP". Make sure that the "Ruby LSP" extension is enabled and configured correctly.

Q: How do I check the Ruby version and path?

A: To check the Ruby version and path, run the following command in the VS Code terminal:

ruby -v

If the Ruby version is not correct, update it to the latest version. If the Ruby path is not correct, update it to the correct path.

Q: What are some additional tips to resolve the issue?

A: Some additional tips to resolve the issue include:

Make sure that you have the latest version of the Ruby LSP extension installed.
Check if there are any conflicts with other extensions that might be causing the issue.
Try restarting the VS Code editor and the Ruby LSP server to see if it resolves the issue.

Q: Can I get help if I'm still experiencing issues?

A: Yes, you can get help if you're still experiencing issues. You can try searching online for solutions, checking the VS Code documentation, or reaching out to the VS Code community for assistance.

By following these Q&A and solutions, you should be able to resolve the error code -32097 and connect to the Ruby LSP server successfully.