Laravel Sail share via expose doesn't seem to function at all

[Jamesking56]

Hi guys,

Trying to share my Laravel site with my phone to do some testing via Laravel Sail.

So I type in sail share and get the usual output. When I visit the dashboard URL that appears on my Mac, I get Site cannot be reached.

When I try to visit the URL generated by sail locally and via my phone, I get ERR_EMPTY_RESPONSE in Chrome.

Not sure whats going on? I'm using Docker Desktop for Mac. Am I doing something wrong here?

[jearsonbgomez]

Hello,

Also in wsl2 not working. Even the the dashboard-url I am getting the ERR_CONNECTION_REFUSED.

[Jamesking56]

I've upgraded this to an actual bug report so hopefully it gets some visibility: https://github.com/laravel/framework/issues/36425

[Jamesking56]

A patch has been issued for Laravel Sail ready for the next release.

[jearsonbgomez]

@Jamesking56 Thanks.

[shortcodes]

Sorry guys but i am still failing to use it. Go newest laravel/sail version v1.4.7. Working on wsl2 ubuntu18 distro and when i click on link provided by command - page is loading forever. In command line I can see my attempts to connect but loading goes forever and never stops. Do I do something wrong?

Regards!

[Jamesking56]

It looks like it has broken again for me too, I think 1.4.7 has undone the fix in 1.4.6.

[Lubje]

Couldn't get it work either with these versions:

• laravel/framework: v8.33.1
• laravel/sail: v1.4.8

[Jamesking56]

Can you comment on the bug issue please https://github.com/laravel/framework/issues/36425

[bjuppa]

Same here, I get sharing to work on Sail v1.4.6 only, so I downgraded to that for now.

[bjuppa]

https://github.com/laravel/framework/issues/36425 has been updated with a description how to fix this!

Basically, make sure you clear out all your beyondcodegmbh/expose-server images from Docker before running sail share again. That will make sure a fresh image is downloaded with correct version.

[bjuppa]

Ah, sorry I misunderstood @davidgittins, yeah you're also seeing that issue with internal urls. First I thought you couldn't get access through the share url at all.

This problem with internal urls is present in every version of laravel/sail that I've tried, so it won't help downgrading, and it won't help deleting expose images from docker either 😞

Let's see what @Lubje comes up with, then we might add an official issue!

[Lubje]

I just checked that I don't have any custom host additions in my project: no proxy, no custom APP_URL setting etc...
Als deleted all the images and rebuild them with the same result, so it seems we have a valid issue here?

[hstandeffer]

I'm also having the issue where expose points to the internal local URL instead of the remote. Would anyone want to add it to the main issues page for Sail? I used Laravel Breeze as well to generate the views if that helps at all

[adgower]

I am also having the same issue: "when I go to the generated url on my phone the first page works, but all the links (like the one for login) are pointed at 'host.docker.internal' instead of the generated one"

[GeorgII-web]

Same, Laravel's functions like route(), Redirect etc. generates 'http://host.docker.internal' instead of 'projectname.laravel-sail.site:8080'.
Looks like docker container gives that domain to Laravel.

[GeorgII-web]

Hi, who has bug with 'host.docker.internal' in a request headers, it could helps.
Had created issue in Sail repo laravel/sail#113

So, Laravel docs was patched by Laravel team:

When sharing your site via the `share` command, you should configure your application's trusted proxies within the `TrustProxies` middleware. Otherwise, URL generation helpers such as `url` and `route` will be unable to determine the correct HTTP host that should be used during URL generation:

    /**
     * The trusted proxies for this application.
     *
     * @var array|string|null
     */
    protected $proxies = '*';

[bjuppa]

Thank you very much @GeorgII-web!

[Lubje]

Thanks @GeorgII-web for creating the issue.

[s-marjanovic-bm]

This saved my life! Thank you!

[diegoldev]

Hi all. Seems that the error comes back with new Expose v2. Anyone facing same issue?

[robertsheacole]

I'm using valet for proxying my urls to the Docker containers. valet share still works.

[m33ts4k0z]

Hi all.

I believe new issues were introduced this year regarding the sail share command on WSL2.

I have also opened an issue here