Last active
January 8, 2020 09:18
-
-
Save abdumu/c1cfc94386af2303f455cacc1606a9a7 to your computer and use it in GitHub Desktop.
"This connection is not private" + "Valet" + "iOS Simulator"
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-1- edit ~/.composer/vendor/laravel/valet/cli/stubs/openssl.conf | |
Change: | |
basicConstraints = CA:FALSE | |
To: | |
basicConstraints = CA:TRUE,pathlen:0 | |
save file. | |
-2- go to your website folder, run: valet secure | |
-3- | |
(old versions) drag ~/.valet/Certificates/[website.domain].crt to iOS simulator to add it there. | |
(new versions) drag LaravelValetCASelfSigned.pem to iOS simulator to add it there. | |
-4- From iOS simulator, | |
- go to Settings->about->Certificates Trust Settings | |
- Enable Full Trust for your website cert. | |
Enjoy |
@if4lcon i don't hv a macos. Does this still work?
Btw, I fixed it by dragging and dropping LaravelValetCASelfSigned.pem in CA folder to the simulator.
@koraykupe good to hear that. I'll update the gist.
no you just need to add LaravelValetCASelfSigned.pem to the simulator you don't need to change anything
thanks Mr. @if4lcon
Somethings LaravelValetCASelfSigned.pem
maybe located in ~/.config/valet/CA
and in iOS 13 you need to install profile first from Setting -> General -> Profile
to see Certificate in Settings -> General -> About -> Certificate Trust Settings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This one was really promising, but...
I did exactly the same steps, but it is not shown on Certificates Trust Settings screen. I am getting crazy.