LAN access with WSL2 #378
-
LRR Version and OS Bug Details I was scouring the closed issues and could only find that Mojolicious default config sets network to I would assume that LRR should work out of box over LAN so I am unsure as to what the issue may be. Matching Logs
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Another note to add is that I am running LRR with WSL v2. I just tested switching back to WSL v1 and I have no issues connecting to the server. It asked me to allow perl access to private/public networks with the file location being I noticed that when running WSL v2, LRR creates an ext4 image, while WSL v1 create a rootfs folder under the Distro folder. |
Beta Was this translation helpful? Give feedback.
-
WSL2 currently has some issues related to localhost access by other machines: microsoft/WSL#4636 For now I'd recommend you stick to WSL1 until said issues are fixed by Microsoft. |
Beta Was this translation helpful? Give feedback.
-
Seems like a firewall issue. Try creating an inbound rule for all programs to allow connection on port 3000 and see if it starts working. I think it specifically has to do with making your firewall rule only allow Karen.exe, because when I test on my own device and configure the rule to allow only Karen.exe through port 3000, it breaks and I also become unable to access my server. e: as you both confirmed, it is a WSL2 bug. But if you configure an open rule on port 3000 while on WSL2, it works fine. |
Beta Was this translation helpful? Give feedback.
-
@huntrshado I noticed that while using WSL1, it creates a firewall rule for perl and not the |
Beta Was this translation helpful? Give feedback.
-
Since there's no real fixable issue on my side, I'll be converting this to a discussion so that others can see it if they run into trouble w. WSL2 installs. Glad you got it sorted out! |
Beta Was this translation helpful? Give feedback.
Seems like a firewall issue. Try creating an inbound rule for all programs to allow connection on port 3000 and see if it starts working.
I think it specifically has to do with making your firewall rule only allow Karen.exe, because when I test on my own device and configure the rule to allow only Karen.exe through port 3000, it breaks and I also become unable to access my server.
e: as you both confirmed, it is a WSL2 bug. But if you configure an open rule on port 3000 while on WSL2, it works fine.