valet: Laravel Valet's Self-signed Certs does not play with Firefox

A fresh install of Laravel Valet and then a valet secure <my site>.

OK, on Chrome, I can get it HTTPS – nice.

However on Firefox (and FirefoxDev), I get the insecure self-signed error. Is this because Mozilla has stricter control or just an error on Valet’s part? Or maybe Chrome has a looser control on self-signed certs. Anyone ever experienced anything like this? (Of course in prod, I would not be using a self-signed cert but that’s beside the case.)

Thanks!

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 15
Comments: 40 (5 by maintainers)

Most upvoted comments

FIREFOX SOLUTION:

Instead of manually adding exceptions separtely for each site served by valet, IMPORT valet’s CA to Firefox’s certificate Authorities: firefox certificate part 1 firefox certificates part 2 firefox certificate part 3

+168

drbyte on Dec 15, 2018

I had to rm ~/.config/valet/CA/* and then valet install before importing the newly created LaravelValetCASelfSigned.pem into FireFox as per the instructions posted earlier.

+11

lasseeee on Oct 20, 2020

Now the accept button is gone on my latest version of Firefox.

+11

hellerbenjamin on Feb 7, 2018

FIREFOX SOLUTION:

Instead of manually adding exceptions separtely for each site served by valet, IMPORT valet’s CA to Firefox’s certificate Authorities:

Thanks a lot @drbyte . Just followed your instructions on the latest Firefox Developer browser on macOS Catalina and it worked really well.

+10

jasperf on Jun 7, 2020

Downloaded the latest Firefox Developer Edition and was able to open Valet sites using the certs it creates. Still able to add each individual site as a security exception

Are ya’ll still using the .dev domain? That domain no longer works unless you’re Google. It stopped working in Chrome back in December and Firefox just added it to the preloaded HSTS lists. So that could be your issue. Try using .test or .localhost (or anything not in the HSTS lists) as your dev domain https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/

AnalogMemory on Feb 17, 2018

Valet adds the certificate as “trusted” in the OSX keychain. However – Firefox uses its own certificate manager, so doesn’t see it.

loganhenson on Feb 17, 2017

I was still using the dev domain. Thanks for the response.

hellerbenjamin on Feb 27, 2018

You don’t need to change TLD. You must completely clear (not remove, only clear) valet, clear everything about valet in KeyChain (I’m using Macos). For clearing keychain you can search “valet” in search box and delete these.

How to clear valet? Let me write all commands.

rm ~/.config/valet/CA/*
rm ~/.config/valet/Certificates/*
rm ~/.config/valet/Nginx/*
rm ~/.config/valet/Sites/*

You need only remove content of these folders. After that you can use valet link and valet secure commands. Valet will create new SSL files in CA and Certificates folder and import these to system certificates. And everything is fine now.

kodmanyagha on Nov 14, 2022

I had to rm ~/.config/valet/CA/* and then valet install before importing the newly created LaravelValetCASelfSigned.pem into FireFox as per the instructions posted earlier.

After I imported the Valet CA certificate nothing changed… found this thread and I realized my certificate had expired as well so removed it as you suggested and installed Laravel Valet again. Thanks for the tip.

jasperf on May 14, 2021

I’m facing the same problem on firefox. But dev domain works well on safari. I change dev domain to local domain, and now I can continue my work. Thanks @AnalogMemory for the link!

aginanjar on Mar 20, 2018

have you tried importing the CA? https://vimeo.com/245172191

andreicristianpetcu on Feb 17, 2018

FF 59 does not offer a solution. I am forced to use another browser now! A self-signed certificate is not accepted anymore! Adding a website as exception does not solve the problem.

Who knows a solution? Is it possible to use another CA?

Kompas on Feb 16, 2018