I've been using Laravel Valet for while, and I've just encountered a situation that is working my last nerve: after creating a new Laravel project, I went to the public directory and did valet link my_project, then valet secure my_project. Now, valet links shows https://my_project.test but when going there, I get "Your connection is not private".
In Chrome, you can click on "Not Secure" and see the certificate, and when I do this, it shows the certificate for a different one of my projects! I have looked at my ~/.config/valet/Certificates directory, and the my_project.test files are all there (.conf, .crt, .csr, and .key). Any helpful suggestions would be most welcome.
Okay—thanks to #Rory, the problem is solved! Here are the steps:
Run composer global update.
Run valet restart.
Do valet unsecure my_project, then valet unlink my_project.
Do valet link my_project, then valet secure my_project
...and Bob's your uncle!
The answer above is correct, but if you are like me and use Firefox, you can get frustrated. The reason for this on Firefox is that this browser manages its certificates on its own, and not using the root certificates from your current computer. Because of this, you are required to import your Valet Root Certificate to the browser to allow this to open Valet website as secure.
Before fixing your browser, is important to know where your Valet setup stores the new CA Certificate:
~/.config/valet/CA/LaravelValetCASelfSigned.pem
I recommend you copy this file on your desktop to find it easily.
To fix your browser and make it work again with Valet you need to:
Open Firefox (Yes, I always assume the browser is closed).
Go to Settings (Triple bar icon on the right top corner) or CMD+,.
Click on Privacy and Security.
Scroll Down until you find Security > Certificates. Click on View Certificates....
On the new screen, Click on Authorities.
Scroll until the end of the screen (Be sure to scroll, because it looks like there's a nested scroll on that screen) until you find the Import... option.
Look for the LaravelValetCASelfSigned.pem file and click Open.
Click Ok and close and reopen your Browser.
Now your Firefox browser should work as expected.
Related
hello preparing a demo for someone,
I have followed the step to install a Prestashop locally on Laragon.
all was working well till the end of installation and installation folder removal.
now all the links are down and I got an error about the SSL certificate that says this website can't offer secure connexion. the answer sends by the website is wrong.
have you already encountered this kind of issue with Prestashop installation and how to get out of this?
You can fix this easily Enabling the SSL certificate built-in with Laragon.
Just right click on the (maybe hided) Laragon icon on the system tray (located at the bottom right in the Windows Taskbar) and then -> Apache -> SSL -> Enabled (be sure after the selection it will be checked then).
Then just click in the same way on -> Apache -> Reload, and then reload the page on the browser to see your https website version in locale.
You probably chose to enable SSL during installation, while your local environment does not come with a trusted certificate.
Anyway you should be able to reach backoffice by trusting the browser alert and disable SSL support from "Advanced parameters" menu.
If not, go direcly in DB (ps_configuration table) and force disabling SSL by setting "PS_SSL_ENABLED" and "PS_SSL_ENABLED_EVERYWHERE" config keys to 0 value.
I published my project's code on development server. Before publishing it, I created a website on IIS it's link 192.168.1.133:601 (localhost)
But on chrome get ERR_UNSAFE_PORT error.
Tried Explorer and Edge browser therefore it works.
Actual Result: On chrome get ERR_UNSAFE_PORT
Expected Result: Website works.
After my long researches, I found some port list this is restircted by Google.
Thus, I realized that, my port in the list then I changed the port.
Link is https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/net/base/port_util.cc
In July 2021, I encountered this problem and most of the standard fixes had already become obsolete (especially the one where you open 'Chrome Properties', since I use a Macbook.)
This is a MacOS-specific workaround, and here are the steps:
First, locate the Chrome icon in your 'Applications' folder, then right-click to select 'Show Package Content'. Double-click, to enter into the sub-folder. Select 'MacOS'. Inside, you'll see the Google Chrome executable. Rename it 'portfix', then open up a terminal.
/Applications/Google\ Chrome.app/Contents/MacOS/portfix --explicitly-allowed-ports={port_you_want_unblocked}
Don't forget to undo all of this when you're done with your tests, as this is a vulnerable way to leave your browser for too long!
In my case I used Port 87 and got the error ERR_UNSAFE_PORT.
After changing the Port the site is working...
I am working on Windows 10, using Ampps. I have created a domain (tps.local) using Ampps Panel with support to SSL. I see it creates a cert, but when I work from Chrome I get Get ERR_SSL_SERVER_CERT_BAD_FORMAT error.
I have tried:
Importing certificate as trusted.
Setting url on Windows trusted sites list.
Changing flag in Chrome to allow unsecure localhost certificate
Setting time adjustment to automatic
Cleared SSL cache.
After every change I have restarted chrome using chrome://restart
Do I have to create a new certificate? I have installed OpenSSL for Windows, but I am not sure (if necessary) how to proceed since Ampps already created a cert.
Fixed problem by self-signing certificate here:
I've entered "somesite.local 192.168.0.2".
Then add domain in ampps panel with SSL checkbox on.
Then replace apache\conf\ssl_key\YOURDOMAIN.key and apache\conf\ssl_crt\YOURDOMAIN.crt with those you got from zerossl.
Note: Don't forget to restart Apache
It's not a solution, but a workaround:
Switch to Firefox, because you can easily ignore the warning there (at least for now - Firefox 58).
I am trying to fix the following issue.
On a Windows 7 machine, I installed the latest version of Firefox (40.0.3). However, when I try to open https://www.google.ch, I get the following error:
sec_error_unknown_issuer.
There is NO button that says
I understand the risks
Other sites, like youtube (using HTTPS), load without errors.
I already deleted the cert8.db file, and the date and time of the machine are also correct.
Any ideas on how to fix this?
Open this chrome URI by pasting or typing this URI in the location/address bar to open the "Add Security Exception" window and check the certificate:
chrome://pippki/content/exceptionDialog.xul
In the location field type/paste the URL of the website
retrieve the certificate via the "Get certificate" button
inspect the certificate via the "View..." button
This question is active at https://serverfault.com/questions/67844/renew-a-ssl-cert-on-iis6. Thanks.
My manager ordered a new wild card cert for our website as our current is expiring in a few days. Now, I am stuck as I cannot figure out how to install it? It is a cert from GoDaddy.com. I have downloaded it to my server. Upon unzipping it I have a PB7 file (intermediate cert) and a CRT file.
I open IIS6, click Properties on the website I want to update (it already has the old SSL Cert on it). Click on the Directory Security tab then the Server Certificate... button.
Now, I am presented with the following options:
Renew the current certificate - was
done manually through GoDaddy and no
pending renewal was ever issued.
Remove the current certificate - does not sound right for us.
Replace the current certificate - possible...
Export the current certificate to a .pfx file
Copy or move the current certificate to a remote server site
Now, when I choose the REPLACE option it presents me with a dialog of already installed certs!!! My new one is not in there.
What the heck do I do? Google/Bing is being of no help to me right now.
https://serverfault.com/questions/67844/renew-a-ssl-cert-on-iis6
This leads to https://serverfault.com/questions/68165/peers-certificate-has-been-revoked
And all is quite on the western front. :(