Answer the question
In order to leave comments, you need to log in
How do you work with WSL 2?
The bottom line is that everything worked for me before. I used the wsl console, and kept all projects on openServer/Laragon , I always installed all dependencies through wsl bash, but recently (After moving to wsl2) my webpack just stopped proxiing to any of the openServer / laragon servers, I put myself on wsl LAMP and everything works fine there, but there are also some restrictions that are inconvenient for me (Several domains do not want to work together, although I did everything according to the guide, which are all the same).
Question: How do you work with wsl2? Is there any point in this at all (Wsl)? Windows is vital, but I can’t understand why my projects are not proxied. How to fix this, or at least how to debug if I have a stupid white screen.
Answer the question
In order to leave comments, you need to log in
A non-working web server has nothing to do with the specifics of WSL - just deal with its config and everything will be ok.
wsl2 is essentially a virtual machine, ports of applications opened in wsl2 are automatically
forwarded
out of the box to the host (but not outside).
If you run an application in windows that opens ports,
this does not mean that they will be forwarded to this virtual machine,
for access you will need to contact the ip address .
You can also set up the whole stack inside wsl2 or in docker for example
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question