lgaticaq / https-proxy-alpine

Use HAProxy to create a HTTPS proxy
Apache License 2.0
1 stars 0 forks source link

"error, no objects specified in config file" #33

Open m35 opened 6 years ago

m35 commented 6 years ago

Thank you for making this Docker container. When running the suggested command in the README, I'm getting errors.

$ sudo docker run -p 80:80 -e PORT=8000 -e HOST=192.168.1.2 -p 443:443 lgatica/https-proxy-alpine
[DOCKER ALERT] No key+cert pair found. Generating a snakeoil one. Remember to use real ones for production. See README.
Generating a 2048 bit RSA private key
..............+++
...........................+++
writing new private key to 'key.pem'
-----
error, no objects specified in config file
problems making Certificate Request
cat: can't open 'cert.pem': No such file or directory
[ALERT] 242/015318 (1) : parsing [/usr/local/etc/haproxy/50-frontend.cfg:10] : 'bind :443' : unable to load SSL certificate from PEM file '/etc/ssl/private/combined.pem'.
[ALERT] 242/015318 (1) : Error(s) found in configuration file : /usr/local/etc/haproxy/50-frontend.cfg
[ALERT] 242/015318 (1) : Fatal errors found in configuration.

Digging deeper, it looked like openssl was having an issue generating the cert.pem file due to the .cnf file. Any suggestions?

Environment

Docker version 17.12.1-ce, build 7390fc6 Running in Ubuntu 18.04.1 LTS Running as guest in VirtualBox Version 5.2.8 Running in host Windows 10

CaptainYarb commented 6 years ago

I also ran into this issue.

lgaticaq commented 6 years ago

Downloading windows 10 iso for fix this

CaptainYarb commented 6 years ago

Could you please clarify?

lgaticaq commented 6 years ago

Sorry i am need download windows 10 for replicate this bug

CaptainYarb commented 6 years ago

Ah I see. For what it's worth we tried this on Ubuntu (Docker doesn't care about the OS)

lgaticaq commented 6 years ago

I tested in Manjaro Linux (4.18.12-1-MANJARO) and not got this issue

CaptainYarb commented 6 years ago

With Docker the OS literally won't affect the way this runs. In the test that @m35 and I ran, we didn't mount any volumes and we didn't set and SSH keys.