Phil Cross Phil Cross - 3 months ago 68
Apache Configuration Question

Laravel routes behind reverse proxy

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 but all the routes, generated using the

helper, are displaying the following url:
and not

The reverse proxy is setup as such:

<VirtualHost *:80>

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

ProxyPass /
ProxyPassReverse /
<Location />
Order allow,deny
Allow from all

I have set the actual domain name in


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.

Answer Source

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

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

if (!empty($proxy_url)) {

if (!empty($proxy_schema)) {

then add the following line into .env file:


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

Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download