Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supplied certificate is viewed as a directory #49

Open
ghost opened this issue Nov 21, 2016 · 4 comments
Open

Supplied certificate is viewed as a directory #49

ghost opened this issue Nov 21, 2016 · 4 comments

Comments

@ghost
Copy link

ghost commented Nov 21, 2016

Hello,
I'm having trouble setting up Docker container, I always get error saying my certificate is a directory.
I checked but it is a normal file. I don't know weather it is my fault or not.

Thanks in advance

Docker version

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 21:45:16 2016
 OS/Arch:      linux/amd64

My config

docker run \
   -d --net="host" \
   -v /PATH/TO/CERT:/etc/letsencrypt/live/xxxxx.xxx/fullchain.pem \
   -v /PATH/TO/CERT_PRIVATE_KEY:/etc/letsencrypt/live/xxxxx.xxx/privkey.pem \
   --ulimit nofile=32768 devsisters/quic-reverse-proxy:releasemode \
      -cert=/etc/letsencrypt/live/xxxxx.xxx/fullchain.pem \
      -key=/etc/letsencrypt/live/xxxxx.xxx/privkey.pem \
      -addr=0.0.0.0 \
      -port=443 \
      -n=4 \
      -loglevel=2 \
      -- http://xxxxx.xxx:443

Log

root@node1 : ~ [0]# docker logs --follow xxxxxxxxxxxxxxxxxxxxxxxxxxxx
2016/11/21 13:28:26 About to listen on 0.0.0.0. Go to https://0.0.0.0:443/
2016/11/21 13:28:26 Starting reverse proxy for backend URL: http://xxxxx.xxx:443
2016/11/21 13:28:26 read /etc/letsencrypt/live/xxxxx.xxx/fullchain.pem: is a directory

Test that my certificate is really a file

root@node1 : ~ [0]# test -f /etc/letsencrypt/live/xxxxx.xxx/fullchain.pem
root@node1 : ~ [0]# test -d /etc/letsencrypt/live/xxxxx.xxx/fullchain.pem
root@node1 : ~ [1]# 
@stvn
Copy link

stvn commented Jul 13, 2017

I'm having the exact same problem. @PSSGCSim were you able to solve this?

@ghost
Copy link
Author

ghost commented Jul 13, 2017

No @stvn, in the end, I just gave up.

@stvn
Copy link

stvn commented Jul 13, 2017

Thanks for the quick reply. Totally understand. This is my 3rd attempt to get this working and have been banging my head on this. I've removed the arguments in an attempt to run it without certificates, and while it's now running, I still can't use it. I'll let you know if I figure it out, in the chance that you're interested in trying again.

@ghost
Copy link
Author

ghost commented Jul 13, 2017

Thank you, if you get working it I will surely try it as well. But currently, I am hoping for NGINX implementation to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant