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

SSL selfsigned httpd: Syntax error #5

Open
davebra opened this issue Jan 21, 2019 · 7 comments
Open

SSL selfsigned httpd: Syntax error #5

davebra opened this issue Jan 21, 2019 · 7 comments

Comments

@davebra
Copy link

davebra commented Jan 21, 2019

There is an error during the creation of the container when using SSL.
I'm using docker-compose to start the container, this is my docker-compose.yml file:

version: '3'
services:
webdav:
image: bytemark/webdav
ports:
- "443:443"
environment:
- SSL_CERT=selfsigned
volumes:
- ./dav:/var/lib/dav
- ./user.passwd:/user.passwd

and this is the docker-compose up log:

webdav_1 | Generating a RSA private key
webdav_1 | ............................+++++
webdav_1 | .....................................................................................................+++++
webdav_1 | writing new private key to '/privkey.pem'
webdav_1 | -----
webdav_1 | httpd: Syntax error on line 159 of /usr/local/apache2/conf/httpd.conf: Cannot load modules/mod_ssl.so into server: Error relocating /usr/local/apache2/modules/mod_ssl.so: SSL_CTX_set_post_handshake_auth: symbol not found
webdav_1 exited with code 1

@tsievers33
Copy link

I'm getting this error too, with signed SSL certs (mountes at /privkey.pem & /cert.pem

@tsievers33
Copy link

tsievers33 commented Mar 27, 2019

I fixed this in a image (cloned from this repo and tagged with httpd:2.4.35-alpine):
twizzel/webdav

This works!

@XNinety9
Copy link

I have this error too

@davebra
Copy link
Author

davebra commented Jun 19, 2019

Hey @deadbird99 , use the docker image twizzel/webdav or clone my version https://github.com/davebra/docker-webdav that uses the old alpine-apache without this issue

@kerphi
Copy link

kerphi commented Sep 11, 2019

@pcammish should just rebuild the 2.4 image (or generate a new version).
It will fixes this issue.

@Kelduum
Copy link

Kelduum commented Sep 13, 2019

I no longer have access to the repo after leaving Bytemark. You may want to contact Bytemark support directly, as someone may still be there who can sort it out.

@kerphi
Copy link

kerphi commented Sep 13, 2019

ping @jamielinux @ianeiloart or @boonen ?

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

5 participants