Can't connect through VSCode remote server

Bug description

Although I have followed the tutorial on this blog to configure JupyterHub to be accessed from Visual Studio Code, I still can’t connect properly. The print('test') command remains stuck in execution, and the cell never finishes processing.
I am trying to access the JupyterHub from my VPN, and the UI works and the notebooks works properly
The ‘jupyter’ log section on VSCode shows the message:

16:09:38.542 [info] Disposing kernel .jvsc74a57bd0916dbcbb3f70747c44a77c7bcd40155683ae19c65e1c03b4aa3499c5328201f1./bin/python3./bin/python3.-m#ipykernel_launcher for notebook ~/Documents/Repositories/helm-charts/jupyter/Untitled.ipynb due to selection of another kernel or closing of the notebook
16:09:38.542 [info] Dispose Kernel '~/Documents/Repositories/helm-charts/jupyter/Untitled.ipynb' associated with '~/Documents/Repositories/helm-charts/jupyter/Untitled.ipynb'
16:09:52.206 [info] Starting Kernel (Python 3 (ipykernel)) for '~/Documents/Repositories/helm-charts/jupyter/Untitled.ipynb' (disableUI=false)
16:09:52.448 [info] https://jupyter-hub.calcard.com.br/user/~.santos/: Kernel started: 2758f471-249c-420e-89f9-5bd4e8c47c9b
16:09:52.997 [info] Started session for kernel startUsingRemoteKernelSpec:7eb14cc8b4637133bba7dc572cac91c7c288c6b483f885d1a6da80fa0c36e515..python3./python./.-m#ipykernel_launcher
16:09:53.125 [info] Kernel successfully started
16:09:53.184 [error] Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer
16:09:53.186 [error] Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer
[...]
16:09:54.803 [error] Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer
16:09:54.805 [error] Exception while handling messages: TypeError: First argument to DataView constructor must be an ArrayBuffer

I’ve checked the firewall, but no block was found.

Am I missing something? Can you help me to solve this issue?

Here follow more information in this Github page issue