Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet fix and valet install after updating and before submitting my issue/feature.

What is the problem?
PHP from console/terminal is different or is using PHP 7.4.3. How do we instruct valet to use a specific php version which minimum is php version 7.2.

What was supposed to happen?
Valet should use php7.4 instead of global or another best solution?

What actually happened?
Nothing. Same PHP 7.4.3 on CLI

How to reproduce this?
I just followed the Installation Guide at WIKI

What is the solution?
Global change (currently breaks valet php >= 7.2)

$ sudo update-alternatives --set php /usr/bin/php7.1
$ php -v

Or you can use:

$ php7.1 -v

Sources
N/A

Reference
Stack Overflow

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-linux (valet --version): <Valet-Linux-Version>
• I've run valet fix and valet install after updating and before submitting my issue/feature.

What is the problem?
I was previously running on WSL 1 and everything was working fine. However, I recently upgraded to WSL 2. I know this doesn't have "official" support for WSL 2 yet, but in terms of Valet everything works fine. The issue appears to be with Acrylic DNS.

When editing my adapter settings, I now have 2 adapters instead of 1 as show below;

I stuck to the first one just called Ethernet and changed my DNS settings to proxy through Acrylic, but the issue is it basically completely kills my internet.

When trying to access any .test domain it fails, and when trying to even access www.google.com I get the error This site can't be reached. As soon as I revert my adapter settings my internet comes back and it's working again (the .test domains still don't work obviously.)

My config and hosts file for Acrylic are completely stock except for the 1 change to add 127.0.0.1 *.test to the hosts file.

Asking here in case anyone else has ran into this problem and been able to fix it somehow.

As a side note, now that we have a separate adapter for WSL 2, we might actually be able to get dnsmasq working and remove the need for Acrylic completely, but I'm not very experienced with networking so I could be wrong.

EDIT:
Although as a secondary thing I just checked, I uninstalled Acrylic and it appears even if I set the .test domain manually in my hosts file like so;
127.0.0.1 my-doman.test
It still doesn't work. If I go directly to 127.0.0.1 I get a 404 - Not Found Valet page, but as soon as I try access my-domain.test I get the error ERR_CONNECTION_REFUSED. So no clue what's going on there? Just to make this more confusing, pinging the url from CMD gets a response.... So I literally have no idea what is going on now and I have no the faintest idea how to fix this. So hopefully someone can provide some input.

EDIT AGAIN:
I just tested downgrading to WSL 1 and followed the installation instructions exactly as they state on the WIki, as well setting my adapter settings and now I CAN load google.com and such, but when attempting to connect to any .test domain, I get the refused to connect. error.

So I'm a bit confused as to what the issue is. Perhaps this just doesn't play nice in general with the new Windows Insider Builds?

Either way though, I think it might be time to start looking into WSL 2. A majority of people I know doing dev work are already using 2 instead of 1 because of how much faster it is, and one of the major benefits of it is "Accessing network applications" which theoretically I think would make dnsmasq work as shown here;
https://docs.microsoft.com/en-us/windows/wsl/wsl2-ux-changes#accessing-network-applications

After installing and using Valet WSL for while without any issues and after a sudo apt-get upgrade im getting a 502 Bad Gateway. I’m not an expert so i have no idea how to fix this.

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-linux (valet --version): <Valet-Linux-Version>
• I've run valet fix and valet install after updating and before submitting my issue/feature.

What is the problem?
There appears to be some misconfigurations in the Nginx files. When sending requests with basically > 1-2 cookies, you get a 502 Bad Gateway along with this error in the Nginx config.
2020/02/12 17:31:03 [error] 3171#3171: *530 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: domain.test, request: "POST /test HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "domain.test", referrer: "https://domain.test/test"

I've found that the solution to this was to increase the buffer size of both proxy and fastcgi as show below;

    proxy_buffer_size 4096k;
    proxy_buffers 128 4096k;
    proxy_busy_buffers_size 4096k;

    fastcgi_buffer_size 4096k;
    fastcgi_buffers 128 4096k;
    fastcgi_busy_buffers_size 4096k;

Is it possible we can get this fixed in the nginx configs that get generated because it's kinda annoying to always have to change this.

When i open valet link giving name with .test it show 404 not found! I tried to add index.php in /home/foldername/.valet/sites/foldername but still show 404 not found

Hi! I'm going to use your modification of valet for my projects. Everything works pretty well on Drupal. But there are issues with debugging. Actually it not stops at breakpoints in project. Does anyone have similar issues? I didn't found any information related wsl xdebug and valet, so I hope someone can help here

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet fix and valet install after updating and before submitting my issue/feature.

What is the problem?
Some dependencies are either missing or changed names.

What was supposed to happen?
Prepare WSL to install all needed php7+ stuff.

What actually happened?

How to reproduce this?
Enable WSL->Download and install Ubuntu 18.04 WSL-> run step 6 of the installation guide: sudo apt-get install network-manager libnss3-tools jq xsel build-essential libssl-dev zip unzip dnsmasq nginx mysql-server php-fpm php-cli php-mysql php-sqlite3 php-intl php-zip php-xml php-curl php-mbstring redis-server php-redis php-pear php-dev pkg-config libz-dev libzip-dev libmemcached-dev libmemcached11 libmemcachedutil2 libmagickwand-dev imagemagick memcached

What is the solution?
Find the missing dependencies

Hi, thank you for your this incredibly helpful package!

Hoping you can help with these questions/issues.

Installation

I wanted to confirm that the proper installation method is:

composer global require valeryan/valet-wsl

I ask because the guide I originally followed to install this said to manually add a repository to the global composer.json (pointing to the dev-master branch) and then run composer global update. Perhaps that is outdated.

Version Discrepancy

I have this installed on two machines, both Windows 10 + WSL1.

On one of the machines, valet --version returns "Valet v3.0.0", while on the other it returns "Valet v1.0.6"

This happens regardless of how I install Valet.

I was actually going to submit an issue to laravel/valet (www subdomains don't work), but couldn't figure out the actual version number I have on this machine due to this issue. I see that 1.0.6 is the latest release of this package.

fix and diagnose commands are not defined

I tried to run valet fix and valet diagnose, but neither command is defined. (Same result on both machines.)

Please can the upstream updates to the composer deps be merged?

PHP Fatal error: Cannot declare class Nginx, because the name is already in use in /home/alex/.composer/vendor/valeryan/valet-wsl/cli/includes/facades.php on line 32

How can I fix this?

Does this support WSL 2 latest release? if it does, would it work the same way?

Hi,

Was wondering if anyone has managed to get a Wordpress multisite setup working correctly using valet-wsl?

I can remember having the same issue when using Valet on a mac and I just needed to use a custom driver to get the URL's to work correctly. However, that custom driver doesn't seem to work on valet-wsl.

Many thanks

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet install after updating and before submitting my issue/feature.

What is the problem?
Not sure why, but when I try to restart my valet I get the following error

Warning: Class 'Tightenco\Collect\Support\Collection' not found in /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/tightenco/collect/src/Collect/Support/alias.php on line 19

Fatal error: Uncaught Error: Interface 'JsonSerializable' not found in /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/tightenco/collect/src/Collect/Support/Enumerable.php:11
Stack trace:
#0 /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/composer/ClassLoader.php(480): include()
#1 /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/composer/ClassLoader.php(346): Composer\Autoload\includeFile('/home/dzoljom/....')
#2 [internal function]: Composer\Autoload\ClassLoader->loadClass('Tightenco\\Colle...')
#3 /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/tightenco/collect/src/Collect/Support/Collection.php(11): spl_autoload_call('Tightenco\\Colle...')
#4 /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/composer/ClassLoader.php(480): include('/home/dzoljom/....')
#5 /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/composer/ClassLoader.php(346): Composer\Autoload\includeFile('/home/dzoljom/....')
#6 [internal function]: Composer\Autoload\ClassLoader->loadClass('Tightenco\\Colle...')
#7 [internal fu in /home/dzoljom/.phpenv/versions/7.4.20/composer/vendor/tightenco/collect/src/Collect/Support/Enumerable.php on line 11

What was supposed to happen?
Valet should restart

What actually happened?
I got an error

How to reproduce this?
I'm using phpenv to change php versions, so my guess is that this has something to do with this. Maybe valet is not recognizing the php version provided by the phpenv.

The php works fine (both CLI and FPM),

I ran into some issues with MySql not having a password and not being able to get mysql_secure_installation to work. As a workaround I used mysqladmin....

I think the issue is...

Run mysql with root user as root

sudo mysql -u root

and/or run

sudo mysql_secure_installation

Everything for me is running normal without extra config

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet fix and valet install after updating and before submitting my issue/feature.

What is the problem?
When i try to install valet-wsl it prompt me and error on the package illuminate/container

What was supposed to happen?
Install walet-wsl

What actually happened?
On my machine composer and Laravel installed the version 7.10.3 of illuminate/container but valet-wsl prompt me ths

Changed current directory to /home/lucarossi/.composer
Using version ^1.0 for valeryan/valet-wsl
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - valeryan/valet-wsl v1.0.5 requires illuminate/container ~5.3|^6.0 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, 6.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.12, v6.18.13, v6.18.2, v6.18.3, v6.18.4, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.2.0, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0] but these conflict with your requirements or minimum-stability.
    - valeryan/valet-wsl v1.0.4 requires illuminate/container ~5.3 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9] but these conflict with your requirements or minimum-stability.
    - valeryan/valet-wsl v1.0.3 requires illuminate/container ~5.3 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9] but these conflict with your requirements or minimum-stability.
    - valeryan/valet-wsl v1.0.2 requires illuminate/container ~5.3 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9] but these conflict with your requirements or minimum-stability.
    - valeryan/valet-wsl v1.0.1 requires illuminate/container ~5.3 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9] but these conflict with your requirements or minimum-stability.
    - valeryan/valet-wsl v1.0.0 requires illuminate/container ~5.3 -> satisfiable by illuminate/container[5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9] but these conflict with your requirements or minimum-stability.
    - Installation request for valeryan/valet-wsl ^1.0 -> satisfiable by valeryan/valet-wsl[v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.0.5].

Installation failed, reverting ./composer.json to its original content.

How to reproduce this?

• Install wsl2
• install Ubuntu distro from the store
• Follow the valet-wsl installation guide

What is the solution?
Support the new version of packages required by Laravel 7

Sources
N/A

When restarting my pc I am unable to run wsl or open my Hyper terminal. The Acrylic DNS service prevents the loading of Bash.

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet install after updating and before submitting my issue/feature.

What is the problem?
A description of what you think the problem is.
valet use [email protected] doesn't work.

What was supposed to happen?
Valet downloads (or finds installed) php 7.4

What actually happened?

This does not affect php -v.
Stopping php8.0-fpm...
Disabling php8.0-fpm...
[[email protected]] is not installed, installing it now via Apt... 🍻
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package [email protected]
E: Couldn't find any package by glob '[email protected]'
E: Couldn't find any package by regex '[email protected]'

How to reproduce this?
Run valet use [email protected].

What is the solution?
Looks like for some reason it's looking to install [email protected] instead of [email protected].

Basic info

• I've checked the issue queue and could not find anything similar to my bug.
• I'm on the latest version of valet-wsl (valet --version): <Valet-wsl-Version>
• I've run valet install after updating and before submitting my issue/feature.

What is the problem?
I followed the guide, installed everything. The set up seems to be working, but I can get only about 1 of 5 requests in the browser to load, others seem to hang and eventually time out.
Also checking the PHP log I get this line every second:

[16-Nov-2020 01:33:35] ERROR: failed to retrieve TCP_INFO for socket: Protocol not available (92)

What was supposed to happen?
Page should load

What actually happened?
Request hang up

How to reproduce this?
Installed Ubuntu WSL. Followed the Valet-WSL guide. Ran valet install and then valet link in the project repo. Opened browser, tried to load the page. First one usually loads fine, other ones hang. Only after about five reloads the page actually loads up.
When I tried the same setup with WSL 2 all is working just fine, however in WSL 2 there is a problem with slow FS speeds when project is stored on Windows FS.

What is the solution?

Sources
This problem seems to be related to these issues:
https://stackoverflow.com/questions/46286420/php7-0-fpm-extremly-slow-on-ubuntu-windows-subsystem-linux
microsoft/WSL#2100
https://www.issacc.com/solution-to-nginx-php-fpm-issues-on-windows-subsystem-for-linux-wsl/
However I checked the valet settings and all seems to be set correctly.