Assistance Required - Internal Server Error and Pointer Functionality Issue with Torizon Support Extension in Visual Studio Code

Technical Support
, , ,
1

Dear Support,

I am writing to seek assistance regarding an issue I have been experiencing with the Torizon support extension for Visual Studio Code. For the past two days, I have been encountering the following error:

“Internal server error :: Error (500) - [Errno 104] Connection reset by peer.”

image
image1916×1036 89.2 KB

I have already taken the following troubleshooting steps, but the issue persists:

Checked my network connection: I have a stable internet connection, and I have verified that there are no connectivity problems.

Restarted Visual Studio Code: I have closed and relaunched Visual Studio Code multiple times to ensure that the error is not due to a temporary glitch.

Disabled other extensions: To rule out conflicts with other extensions, I disabled all other extensions temporarily. However, the error still persists.

Additionally, I have noticed that the Portainer functionality is not working as expected:

image
image1449×663 13.5 KB

These issues have only recently started occurring, and I would greatly appreciate your assistance in resolving them. If there are any known server issues or maintenance activities that might be affecting the Torizon support extension, please provide relevant information.
Also, I did not close the portainer, but there is no docker running on my SoM:

torizon@verdin-imx8mm-07219010:~$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

torizon@verdin-imx8mm-07219010:~$ docker ps -a
CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS                      PORTS               NAMES
87da19826903        385713b32362                         "/bin/sh -c 'stdbuf …"   6 minutes ago       Exited (0) 4 minutes ago                        main_arm64v8-wayland-base-vivante-no-ssh_bullseye_debug_41da02b7-a572-4f09-8e97-880fabc33806_latest_instance
dddc1cbb4d5b        torizon/chromium                     "/usr/bin/start-brow…"   2 days ago          Dead                                            torizon_kiosk_1
6d7e7f5e2b43        portainer/portainer-ce               "/portainer --templa…"   2 days ago          Dead                                            torizon_portainer_1

Thank you for your attention to this matter. I look forward to your guidance and support in resolving these problems.

Best regards,
Mehrdad

2

Hi @Mehrdad ,

For the past two days, I have been encountering the following error:
“Internal server error :: Error (500) - [Errno 104] Connection reset by peer.”

We need more information about this issue to better help you:

  • Did you try removing your module from the list of connected devices on the extension, then adding it again?
  • You appear to use V1 of the extension. When does this error occur exactly? When trying to debug using the extension, or when trying something else?
  • What version of TorizonCore is installed on the module? Are you using a Verdin Mini?
  • What OS are you using for your host machine? If you’re on Windows, what is the version of Docker Desktop?

Best regards,
Lucas Akira

3

Hi @lucas_a.tx,

  • Did you try removing your module from the list of connected devices on the extension, then adding it again? Yes, I removed and reinstalled it twice, attempting to add it using both the IP address and the System-on-a-Module (SoM) part number.

  • You appear to use V1 of the extension. When does this error occur exactly? When trying to debug using the extension, or when trying something else? After clicking the “RUN” icon, occasionally it functions correctly, but at times I have to rerun it two or three times.

  • What version of TorizonCore is installed on the module? Are you using a Verdin Mini? TorizonCore 5 and verdin imx8 mini

  • What OS are you using for your host machine? If you’re on Windows, what is the version of Docker Desktop? Yes, windows with docker version: 4.16.3 (96739)

Best regards,
Mehrdad

4

Hi @Mehrdad ,

After clicking the “RUN” icon, occasionally it functions correctly, but at times I have to rerun it two or three times.

So, if I understood this right, the error doesn’t happen every time you try to run/debug your project, is this correct? Maybe it could be a local network problem between the host and the module? I don’t think the extension needs a constant connection to our servers in order to function correctly, but I’ll verify this with the team.

Yes, windows with docker version: 4.16.3 (96739)

OK, just keep in mind that our IDE extension V1 is currently not working with Docker Desktop 4.19.0 on Windows, so I recommend not updating it to this version for now.

About Portainer not working: you can see the container logs by running docker logs torizon_portainer_1 on the module to see what happened. Given that Portainer creates a server on your local network, it’s possible that the cause of the issue is also related to local connectivity.

Can you try testing on a different network, if possible?

Best regards,
Lucas Akira

5

Hi @Mehrdad ,

is there any news on that topic?

Best Regards
Kevin

1 Like
6

Hi @kevin.tx ,

I resolved the issue by reflashing the SoM, and everything is back to normal. It was difficult to determine if the problem was related to our network, the SoM, or TorizonCore.

Thank you so much for your Support.

Best regards,
Mehrdad

1 Like