Most browsers will also have some kind of “Advanced” button which you can click for more details. Here are a couple of examples:ĮRR_CERT_DATE_INVALID or MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT They’ll often be in all caps with underscores. If things go wrong, it’s helpful to have a rough checklist of what to inspect, so let’s review the tools you have to zero in on the problem.įor any errors you encounter, make a note of the actual error message that the browser reports. In most cases, clicking the “Trust” link within Local will create and configure the Local site so that you can access it over HTTPS. If you’re curious and want to know more about what those hosts are doing under the hood, their support documentation is quite helpful:īut this is a help-doc about Local, so let’s take a look at how Local manages SSL certificates for local environments. Both Flywheel and WP Engine make it easy to configure SSL on their managed WordPress platforms. The easiest, and oftentimes, best thing to do is just let a good hosting company handle the setup of SSL for your production sites. Setting this sort of thing up by hand is complicated. To be clear, Local has no way of managing the SSL certificates for remote environments.įor a production server, you’ll likely want to use a certificate that comes from a trusted certificate authority. SSL for remote environmentsīecause Local is an off-line development tool, you might be wondering how you work with SSL for your live site. When talking about SSL and Local, we’ll mostly be talking about self-signed certificate, which is roughly the same as a hand-written badge.īy having Local create and use self-signed certificates, we get the benefit of quickly getting a site to work over HTTPS while not having to pay for and configure a certificate that comes from a third-party certificate authority. Just as there are different kinds of ID cards, there are different kinds of SSL certificates. By having participants create their own name-badge, you get the benefit of quickly identifying strangers, while not forcing them to go to the great effort of working with a government agency for an ID card.Įach of the above examples is like an SSL certificate. Think back to any conference or Meetup you’ve attended. It’s important to remember that just because we trust a hand-written badge less than other forms of identification, doesn’t mean that it isn’t useful! The main reason for this is that a “third-party” has gone to the effort to verify that I am who I say I am. Many of us will likely trust the driver’s license or passport over a hand written badge. Going through the effort to get one of those items is much more complicated and as a result those forms of ID are harder to fake. It’s easy for me to write my name (or any name!) on a name badge and use that as my “ID.” That’s not the case with a passport of drivers license. When comparing the name on those pieces of identification against what I say my name is – which one do you trust more? A hand-written badge with my name on it.What if I gave you three pieces of identification to prove who I am: A lot of those concepts can be abstract, so let’s take a look at a real-world analogy that doesn’t involve computers.
0 Comments
Leave a Reply. |