devsisters / goquic

QUIC support for Go
http://devsisters.github.io/goquic/
BSD 3-Clause "New" or "Revised" License
944 stars 100 forks source link

Supplied certificate is viewed as a directory #49

Open ghost opened 7 years ago

ghost commented 7 years ago

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 commented 7 years ago

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

ghost commented 7 years ago

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

stvn commented 7 years ago

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 commented 7 years ago

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