Open alwaysblank opened 2 years ago
Relevant Slack thread: https://hmn.slack.com/archives/C03K3J34A/p1658433975359989
You need the proxy container to have the necessary certs, and you therefore probably can't run an Altis project at the same time as a local-vip one unless you're using the altis.dev
TLD for it.
It is probably worth trying to port across the changes from these 2 PRs to add mkcert support for handling HTTPS with custom domains and TLDs easy:
The new SSL command is available in the Altis v12 beta currently, or master branch of altis/local-server.
This is technically still "open" until 2.0 is released.
In my case, after setting up
local-vip
and running the cert-build command as described in the README, I was unable to access my site: All browsers returned aERR_SSL_UNRECOGNIZED_NAME_ALERT
.The
altis-proxy
docker container was also throwing errors like this:Ultimately the following steps solved the problem for me but they are not really generalizable at this time:
vendor/humanmade/local-vip/.bin/build-cert.sh
to remove the linemv ${DOMAIN}.crt ${PWD}/${DOMAIN}.crt
because it attempts to move a file to itself, an action which fails and halts the entire scriptbash .bin/build-cert.sh nxs.local
vendor/humanmade/local-vip/nxs.local.crt
into my OS via Keychain Access, and then tell my system to trust itThis was caused by a couple things:
bash
commandlocal-vip
for a new projectlocal-server
more or less "just works" and creates every project onaltis.dev
(from my recollection--I may be wrong) so potentially this should be modified to do the same, with instructions for how to deviate from that, if necessary (and ideally with a more streamlined process).My understanding is that the proxy and traefik can be used for this, but my grasp of both those things is very limited.
Additionally, the script to build certs contains direct references to Nexstar. So far as I can tell these don't cause any problems on their own, but they should probably be removed.