Posted on under Laravel by Owen Conti.
A couple years ago, I was working on a Laravel application that provided Google SSO authentication. However, I ran into a problem when setting up my local redirect URL within the Google UI: they only allow HTTPS URLs. This was a problem because my local development environment was running on HTTP. I needed a way to run my local Laravel application on HTTPS.
If you're running Laravel Valet, setting up HTTPS is as a simple as running the following command:
1valet secureAfter that, update your APP_URL in your .env file to use https, and that's it!
Last year I started using Laravel Sail for my local development environment due to working on multiple projects with different dependency versions (PHP, MySQL, Postgres, etc). One of the first problems I ran into with Laravel Sail was getting HTTPS to work locally. Thankfully, Caddy makes this easy to do.
Let's take a second to review how Laravel Sail serves apps. By default, the docker-compose.yml file uses the APP_PORT environment variable as the port to serve the app on. So for example, if your APP_PORT=1005 then your app will be served on http://127.0.0.1:1005 by Laravel Sail.
You'll need to have Caddy installed on your machine. You can do so via Homebrew:
1brew install caddyIf you don't want to use Homebrew, you can follow the instructions on the Caddy site to build from scratch.
To enable HTTPS for the app running on that 1005 port, we set up Caddy to reverse proxy from a custom domain to the app running on that port. Here's what the Caddyfile would look like:
1my-app.localhost {2 reverse_proxy 127.0.0.1:10053}Then you just need to start Caddy (make sure you don't have nginx or any other web server running on port 80) with: caddy run. This will start Caddy in the foreground of your terminal. You should now be able to load https://my-app.localhost in your browser. It'll take a second for it to load because Caddy will generate a self-signed certificate for the domain, but you should see your Laravel app running on HTTPS!
If you want to run Caddy in the background, you can use the following command to run Caddy after configuring the Caddyfile:
1caddy startFeel free to put your Caddyfile wherever you like. I put mine in the ~/development directory. You just need to make sure you run Caddy from the directory where the Caddyfile is located or you provide the path to the config when you run Caddy.
If you typically use the php artisan serve command to serve your Laravel app locally, you can still run it over HTTPS with Caddy. Add a single entry to the Caddy file using the 8000 port:
1laravel.localhost {2 reverse_proxy 127.0.0.1:80003}This will allow you to start your Laravel app with php artisan serve but have it served over HTTPS.
This part is not necessary, but if you also want to run Vite over HTTPS, you can do so via the vite-plugin-mkcert package. This package will generate a self-signed certificate for your Vite server to run on HTTPS. Here's how you can set it up:
1npm i -D vite-plugin-mkcertThen update your vite.config.js file to use the plugin:
1import mkcert from 'vite-plugin-mkcert';2 3export default defineConfig({4 plugins: [mkcert()]5})One common problem you may run into is with Laravel knowing that it is being served over HTTPS instead of HTTP. Since Caddy is terminating the HTTPS connection for us, Laravel is technically still being served via HTTP. The fix for this is to set your TrustProxies middleware to trust the Caddy IP address. Locally, I usually just set this to *:
1return Application::configure(basePath: dirname(__DIR__))2 ->withMiddleware(function (Middleware $middleware) {3 $middleware->trustProxies(at: '*');4 });Hopefully you found this article useful! If you did, share it on Twitter!
Found an issue with the article? Submit your edits against the repository.