Laravel routes behind reverse proxy

Question

Ok, so for development purposes, we have a dedicated web server. It's not currently connected directly to the internet, so I've setup an apache reverse proxy on another server, which forwards to the development server.

This way, I can get web access to the server.

The problem is, the routes in Laravel are now being prefixed with the internal server IP address, or the servers computer name.

For example, I go to http://subdomain.test.com but all the routes, generated using the route() helper, are displaying the following url: http://10.47.32.22 and not http://subdomain.test.com.

The reverse proxy is setup as such:

<VirtualHost *:80>
    ServerName igateway.somedomain.com

    ProxyRequests Off
    <Proxy *>
        Order deny,allow
        Allow from all
    </Proxy>

    ProxyPass / http://10.47.32.22:80/
    ProxyPassReverse / http://10.47.32.22:80/
    <Location />
        Order allow,deny
        Allow from all
    </Location>
</VirtualHost>

I have set the actual domain name in config\app.php.

Question

How can I set the default URL to use in routing? I don't want it using the internal addresses, because that defeats the point of the reverse proxy.

I've tried enclosing all my routes in a Route::group(['domain' ... group, which doesn't work either.

score 32 · Accepted Answer · edited Feb 10 '20 at 04:11

I ran into the same (or similar problem), when a Laravel 5 application was not aware of being behind an SSL load-balancer.

I have the following design:

client talks to an SSL load balancer over HTTPS
SSL load balancer talks to a back-end server over HTTP

That, however, causes all the URLs in the HTML code to be generated with http:// schema.

The following is a quick'n'dirty workaround to make this work, including the schema (http vs. https):

Place the following code on top of app/Http/routes.php

In latest version of laravel, use web/routes.php

$proxy_url    = getenv('PROXY_URL');
$proxy_schema = getenv('PROXY_SCHEMA');

if (!empty($proxy_url)) {
   URL::forceRootUrl($proxy_url);
}

if (!empty($proxy_schema)) {
   URL::forceSchema($proxy_schema);
}

then add the following line into .env file:

PROXY_URL = http://igateway.somedomain.com

If you also need to change schema in the generated HTML code from http:// to https://, just add the following line as well:

PROXY_SCHEMA = https

In latest version of laravel forceSchema method name has changed to forceScheme and the code above should look like this:

if (!empty($proxy_schema)) {
    URL::forceScheme($proxy_schema);
}

It is called a [scheme](https://tools.ietf.org/html/rfc1630), not a schema. — zrhoffman, Sep 02 '19 at 00:18
this answer needs to be updated. app/Http/routes.php no longer exists — eylay, Nov 04 '19 at 15:09

score 13 · Answer 2 · answered Apr 28 '15 at 08:13

Ok, so I got it. Hopefully this will help someone in the future.

It seems like Laravel ignores the url property in the config\app.php file for http requests (it does state it's only for artisan), and it instead uses either HTTP_HOST or SERVER_NAME provided by apache to generate the domain for URLs.

To override this default url, go to your routes.php file and use the following method:

URL::forceRootUrl('http://subdomain.newurl.com');

This will then force the URL generator to use the new url instead of the HTTP_HOST or SERVER_NAME value.

score 9 · Answer 3 · answered Jan 13 '21 at 08:08

9

Go to app/Http/Middleware/TrustProxies.php and change the protected variable $proxies like this:

protected $proxies = ['127.0.0.1'];

Just this! Be happy!

answered Jan 13 '21 at 08:08

Daniel Sá

156
1
2

1

If you don't care about the security implications this is also possible now: `protected $proxies = '*';` – dcbarans Apr 08 '21 at 16:48
2

This is the modern answer. See https://laravel.com/docs/5.8/requests#configuring-trusted-proxies – Simon Sep 17 '21 at 09:30
Same response! thx! – Daniel Sá Oct 07 '21 at 19:07

score 6 · Answer 4 · answered May 25 '21 at 20:15

Because laravel route is created not from the config/app itself rather than from the server. My solution is adding the proxy_set_header Host to the nginx's config.

server {
    listen 80;
    server_name my.domain.com;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host  my.domain.com;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://127.0.0.1:8000;
    } 
}

i'm using laravel 8 with nginx docker inside a running nginx on the machine, so yeah it's double nginx

After I set the Host header proxied to my docker container it finally worked. So there was no need to change any file in the project, but server config — fluid undefined, Dec 18 '22 at 06:48

Mohammad Gitipasand · Answer 5 · 2022-04-09T04:41:52.850

4

add this code in App\Providers\AppServiceProvider class

if (Str::contains(Config::get('app.url'), 'https://')) {
    URL::forceScheme('https');
}

edited Apr 09 '22 at 04:41

answered Feb 10 '21 at 19:03

Mohammad Gitipasand

340
3
9

score 2 · Answer 6 · edited May 23 '17 at 12:18

2

Seems the Laravel have more convinient solution.. Check answer there: How do I configure SSL with Laravel 5 behind a load balancer (ssl_termination)?

edited May 23 '17 at 12:18

Community

1
1

answered Apr 14 '17 at 12:23

Alex

1,297
1
16
12

score 0 · Answer 7 · answered Aug 22 '18 at 15:14

0

Following up @TimeLord's solution:

In latest version of laravel the name for forced schema has changed and now it is: URL::forceScheme()

answered Aug 22 '18 at 15:14

Giorgi Ghughunishvili

5
2

score 0 · Answer 8 · answered Nov 07 '18 at 13:20

I know this topic is old a.f but I've been solving this issue by replacing the following line in my DatabaseSessionHandler.pdf [@Illuminate/Session]:

    protected function ipAddress()
    {
        return $_SERVER['HTTP_X_FORWARDED_FOR'];
//        return $this->container->make('request')->ip();
    }

Of course you need to migrate the sesssion table first and set up the config
(.env Variable SESSION_DRIVER=database)

score 0 · Answer 9 · answered May 19 '21 at 02:47

For nginx, you don't need to do anything extra in Laravel. The fix can be done at from nginx config;

server {
    listen 80;
    listen [::]:80 ipv6only=on;

    server_name sub.domain.dev;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host  sub.domain.dev;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://127.0.0.1:8000;
    }
}

score 0 · Answer 10 · answered Mar 26 '22 at 00:53

Figured out a way that much cleaner and only does exactly what the loadbalancer tells it to, add this function to your RouteServiceProvider

protected function enforceProtocol()
{
    if(request()->server->has('HTTP_X_FORWARDED_PROTO')){
        URL::forceScheme(request()->server()['HTTP_X_FORWARDED_PROTO']);
    }
}

and in the boot section, simple call it like so

public function boot()
{
    $this->enforceProtocol();
    //other stuff
}

Laravel routes behind reverse proxy

10 Answers10

Linked