caleb-at-pieces
commented
1 month ago Hello @hope205 , I recently have updated these docs to show there is another strategy you can do to resolve this problem, hopefully it will have a higher success rate than the firewall rule:
You can read about it on our docs page here: https://docs.pieces.app/product-highlights-and-benefits/connecting-to-a-remote-pieces-os-instance#pieces-os-is-not-connecting-on-wsl
The section about enabling mirrored networking mode for your WSL instance is what you are looking for. Following that guide you should be good to go, please let me know otherwise! If needed we could definitely hop on a call and debug this together, that will probably lead to the fastest resolution, you can schedule with me here: https://calendar.app.google/9Mj3jqt7syq3y4mX6
As a note: mirrored networking for WSL does not work on Windows 10, you must have Windows 11 installed. Also, you can check if mirrored networking is enabled by running the following command on a WSL terminal: wslinfo --networking-mode
hope205
Software
VS Code
Operating System / Platform
Windows
Your Pieces OS Version
10.0.0
Early Access Program
Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.
I encountered this issue while trying to use the piece extension in my WSL. The piece's extension gives issues anytime I try to use it in the Ubuntu remote desktop environment. This is an image of the issue it shows. I already tried the troubleshooting method on your website by creating a new port but it still didn't work.