Closed nlarche closed 5 years ago
It sounds like the root issue is the certs not showing up in /etc/nginx/certs in the container, that would explain them not being in the config too. I'm not sure how that'd happen, unless Dinghy is somehow getting confused about where your home dir is maybe. Do you see the ~/.dinghy/certs mount in docker inspect dinghy_http_proxy
output?
Thanks for your answer, yes /certs folder seems to be mounted...
Maybe the NFS mount isn't working, have you tried using any volumes mounted from the host yet on your Dinghy install?
dinghy status
show that NFS is running?dinghy ssh
and then ls /Users/nicolaslarche/.dinghy/certs
you should see the certs from within the docker-machine VM too, if NFS is working.ok, I see what happened, I change
export DINGHY_HOST_MOUNT_DIR=/Volumes/Data/...
export DINGHY_GUEST_MOUNT_DIR=/Volumes/Data...
So my home directory is not mounted anymore.
Can I share both my home directory and my project directory in /Volumes
?
or maybe, It's possible to add an environment variable to specify certs directory ?
Oh dang, that stinks. Good catch, your fix looks reasonable.
Hi,
I'm currently not able to activate SSL with dinghy.
I've one container with
VIRTUAL_HOST: www.dyb.dev
and I've generated his certificate with
openssl req -x509 -newkey rsa:2048 -keyout www.dyb.dev.key \ -out www.dyb.dev.crt -days 365 -nodes \ -subj "/C=US/ST=Oregon/L=Portland/O=Company Name/OU=Org/CN=www.dyb.dev" \ -config <(cat /etc/ssl/openssl.cnf <(printf "[SAN]\nsubjectAltName=DNS:www.dyb.dev")) \ -reqexts SAN -extensions SAN
Trying to connect to
https://www.dyb.dev
always return :Failed to connect to www.dyb.dev port 443: Connection refused
And the nginx config which have SSL missing (docker exec -it dinghy_http_proxy cat /etc/nginx/conf.d/default.conf) and certs missing in /etc/nginx/certs
any clue to explain why ssl is missing from the nginx config file ?
Dinghy 4.6.5 docker-machine version 0.16.1
thx