Valet: Share not working on macOS 10.15 Catalina

[erikgaal]

Running valet share is not working for me, it produces the following output. Sites and other functionality seems to be working fine.

~ valet share
sudo: unknown user: ECC33916-7D8F-4341-8C20-69354132C131
sudo: unable to initialize policy plugin
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused

In Request.php line 1028:

  Unable to connect to "http://127.0.0.1:4040/api/tunnels": 7 Failed to conne  
  ct to 127.0.0.1 port 4040: Connection refused                                


fetch-share-url

I'm running v2.3.3 on macOS Catalina Public Beta 2 build 19A501i.

[bmw27]

I'm having the same problem when running valet share.

My specs:

• macOS Mojave v10.14.5
• Laravel Valet v2.3.3

$: valet share
Password:
NAME:
   http - start an HTTP tunnel

USAGE:
   ngrok http [command options] [arguments...]

DESCRIPTION:
   Starts a tunnel listening for HTTP/HTTPS traffic with a specific hostname.
   The HTTP Host header on incoming public requests is inspected to
   determine which tunnel it matches.

   HTTPS endpoints terminate TLS traffic at the ngrok server using the
   ngrok.io certificates. The decrypted, HTTP traffic is then forwarded
   through the secure tunnel and then to your local server. If you don't want
   your TLS traffic to terminate at the ngrok server, use a TLS or TCP tunnel.

EXAMPLES:
   ngrok http 8080                      # forward ngrok.io subdomain to port 80
   ngrok http example.com:9000          # forward traffic to example.com:9000
   ngrok http -subdomain=bar 80         # request subdomain name: 'bar.ngrok.io'
   ngrok http -hostname=ex.com 1234     # request tunnel 'ex.com' (DNS CNAME)
   ngrok http -auth='falken:joshua' 80  # enforce basic auth on tunnel endpoint
   ngrok http -host-header=ex.com 80    # rewrite the Host header to 'ex.com'
   ngrok http file:///var/log           # serve local files in /var/log
   ngrok http https://localhost:8443    # forward to a local https server

OPTIONS:
   --auth               enforce basic auth on tunnel endpoint, 'user:password'
   --authtoken          ngrok.com authtoken identifying a user
   --bind-tls "both"    listen for http, https or both: true/false/both
   --config             path to config files; they are merged if multiple
   --host-header        set Host header; if 'rewrite' use local address hostname
   --hostname           host tunnel on custom hostname (requires DNS CNAME)
   --inspect            enable/disable http introspection
   --log "false"        path to log file, 'stdout', 'stderr' or 'false'
   --log-format "term"  log record format: 'term', 'logfmt', 'json'
   --log-level "info"   logging level
   --region             ngrok server region [us, eu, au, ap, sa, jp, in] (default: us)
   --subdomain          host tunnel on a custom subdomain

ERROR:  Tunnel 'command_line' specifies an invalid or malformed address 'endgame.test:80': strange hostname

Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused
Failed to connect to 127.0.0.1 port 4040: Connection refused

In Request.php line 1028:

Unable to connect to "http://127.0.0.1:4040/api/tunnels": 7 Failed to connect
to 127.0.0.1 port 4040: Connection refused

fetch-share-url

[drbyte]

@bmw27 is yours really about Catalina like this issue is?

I think yours is more similar to #790, particularly since the ERROR: Tunnel 'command_line' specifies an invalid or malformed address matches #790.

[bmw27]

@drbyte My bad 😅 Is there a way to move a comment to different issue? Since there's already been a lot of talk is issue #790, I'm not sure my error output will be of much use.

[drbyte]

@bmw27 Unfortunately no. You could click Edit on this one, copy it to clipboard, and paste it as a new comment on the other issue, and then decide whether to delete the one here or leave it.

The output you posted here doesn't add anything more than a "me too", although that itself has value.

I do wish there was a way to find a common denominator among the affected people's computers, as I can't replicate the problem on either of my Mojave Macbooks. It'd also be helpful if you'd add context around when you installed Valet, how long this problem has been happening (and if it was not a problem "before", and what "before" means), how long your OS has been installed vs new vs upgraded from older versions, etc ... basically anything that might give clues as to how to recreate this situation on another macbook.

[drbyte]

@erikgaal Are you using Hyper instead of iTerm or terminal.app?

[erikgaal]

@drbyte I was definitely using Hyper.app, but I'm pretty sure I tried it in the PHPStorm terminal too.

[apertureless]

@erikgaal

I experienced the same error in hyper on mojave. Try it in the normal terminal or iTerm. Using iTerm somehow solved it for me. ¯_(ツ)_/¯

[mattstauffer]

Gonna call this the Hyper issue for now. If anyone has the problem in PHPStorm, please open up a new issue. Thanks all!