I've setup a docker app in my server and I'm using webinoly to proxy it, which works fine and I can access the site with HTTP, but when I try to generate an SSL for it, I'm asked for the "-root-path" option, however, I'm not even sure where should I point this to because the app is started with a docker-compose file. My Docker app works at localhost:8080 but other than that, I'm confused about the -root-path option.
Yes yes, I've read the docs. I've tried "site site.com -ssl=on" and I get this:
site site.com -ssl=on
[ERROR] Seems like you are trying to request an SSL Certificate for a Parked/Mapped Domain.
Please, use the '-root=domain.com' parameter to specify the main domain.
If your site is using the Reverse Proxy configuration, please use the '-root-path=/opt/app' option.
I've tried using -root-path=/use/share/myapp which is where the docker files are, but it's still not working. Any help is appreciated.
Por cierto, muchas gracias por crear webinoly. Lo uso hace muchos años pero nunca he tenido que hacer algo como lo que intento hacer. Saludos!
I have never used Docker with Webinoly. But here are two suggestions:
EDIT: Due to the docker virtual isolation the first option may NOT work. In fact, I think that it will be very hard to make Webinoly work with Docker. The most optimal solution should be having certbot and other tools inside the docker enviroment, and that's not possible with Webinoly. If you have any experience, please tell us...
The first option didn't work at all because none of the Docker files are directly exposed to the Internet in any way. The documentation suggests using -manual=http however, this also won't work because of how Docker works.
The correct way to generate an SSL for a docker instance is running the following command:
site domain.com -ssl=on -manual=dns
Maybe you could add this to the docs for people that want to use Docker and generate an SSL?
Anyways, thanks for your help!
I have never mentioned Docker in the Webinoly docs because they are not supposed to work together. A web server based on docker is an entirely different approach, you can see the EasyEngine V4 project, for instance.
And yes, I understand.
Just for the record: SSL certs with manual validation are not renewed automatically. You should do it "manually" before they expired (90 days). That's why I mentioned EasyEngine.
PayPal · GitHub Sponsors · Bitcoin