https:// URLs you need to generate certificates, luckily VVV has you covered.
Setting up the Certificate Authority
Using VVV 2.2+ ( switch to
develop branch if it hasn’t been released yet ), then add
tls-ca as a utility under
core, like this:
utilities: core: - memcached-admin - opcache-status - phpmyadmin - webgrind - trusted-hosts - tls-ca
vagrant reload --provision. When this finishes, every site using the
wordpress-develop will have a certificate and support
Visit your site with
https, and you’ll notice that the first time it loads, the browser will complain about an invalid certificate authority. Skip this screen, and it should never show again. This should happen for each new site. See the section below, on accepting a certificate authority to prevent this from happening.
wordpress-default is deprecated, switch to
custom-site-template or create an additional site using the custom site template.
Adjusting Site Templates
Non-official site templates will need to adjust their
vvv-nginx.conf to reference the certificates. Certificates are stored in a
certificates subfolder of the VVV install, available in the VM at
/vagrant/certificates/. Each site has a subfolder, with a
dev.key and a
For example, a site named
example, will have the following files:
Adding a Certificate Authority Certificate
Once the main authority certificate is accepted, all certificates VVV generates will always be accepted. The details of how to do this will depend on your platform, but to do so you will need to know where the certificate is located.
You can find the central certificate in
certificates/ca/ca.crt. There are some caveats though:
- This only works for your instance of VVV, you cannot use this to generate certificates for other VVV users
- This will only work on your machine, this cannot be used to generate an SSL certificate for a live website
- This will never work for
.devdomains, Google have preloaded Chrome with security policies, and Firefox has followed suit. These cannot be dismissed. Since the
.devTLD is owned and used by Google it isn’t safe, switch to