Closed mkantautas closed 5 months ago
I'm also on WSL <3. I have observed this couple times. Interestingly enough, I found that php artisan dump-server
was running when inspecting with ps aux | grep dump-server
even thou no open terminal was present.
Since the dump server binds to IP and listens, starting another session simply doesn't help as the first one already bound and thus is receiving all the dumps.
Find running process with ps aux | grep dump-server
and kill it with kill [pId of the process]
You don't need to reboot PC if you want to restart WSL. This may be helpful at times.
If you're on WSL 2, you may restart WSL with wsl --shutdown
from Windows Run (Win + R).
If you're on WSL 1, you may restart LxxsManager services. Open services.msc
and find there.
I am using windows 10 pro wsl (ubuntu 18.04lts) with valet for linux and occasionally the laravel dump stops working - both(the cli and on page).
The only thing that helps it work again for a while is restarting the OS.
restarting php7.4-fpm, nginx, valet, clearing composer dump or clearing cache... Nothing works.