Torizon IDE Extension for VSCode does not start

Technical Support
,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

This error suggests an issue with the Torizon IDE extension’s data provider registration. Based on the troubleshooting documentation and community experiences, here are the steps to resolve this issue:

Check Internal VS Code Logs

First, check the internal VS Code logs to identify the root cause(1). Open the VS Code command palette and select Developer: Toggle Developer Tools(1). This will open a new window - click on the Console tab and check the logs for any specific error messages(1).

Extension Reinstallation

Based on community experience, manually removing and reinstalling the extension can resolve this issue(2). One user reported: “I manually deleted the extensions from it’s directory location. Installed the Torizon extension again on VS Code (Windows) and it asked me to install it in WSL. I did so and now it seems to be working fine”(2).

WSL-Specific Troubleshooting

Since you’re experiencing this on both Ubuntu 22.04 and WSL2 Ubuntu 24.04:

  1. Verify WSL Connection: Make sure you’re launching Visual Studio Code from a WSL terminal using the command code .(2). Check the bottom left corner of VS Code to confirm it shows the WSL distribution name(2).

  2. Network Configuration: Ensure both your development machine and target device are connected to the same network(2). If you’re switching between networks (home/office), this could affect the extension’s functionality(2).

Port Accessibility Check

Verify that the required ports are accessible between your machine and any development board(1):

  • 22 (Dev Board SSH Connection)(1)
  • 2375 (Docker API)(1)
  • 5002 (Local Docker Registry)(1)
  • 2222 (Container SSH Connection)(1)

Host IP Configuration

If you’re using VPN or have multiple network interfaces, set the torizon.overwriteHostIp setting in VS Code global settings to the correct IP address from your main interface(1).

Try these steps in order, starting with checking the internal logs to get more specific error information, then proceeding with the extension reinstallation if needed.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.