poidl opened a new issue #2955: URL: https://github.com/apache/apisix/issues/2955
Related: https://github.com/apache/apisix/issues/2923 I upgraded from 2.0 to 2.1 and have the same issue: ``` Dec 03 15:14:10 mymachine systemd[1]: Started apisix. Dec 03 15:14:10 mymachine start_apisix.sh[295]: lua: ./bin/apisix:255: missing ssl cert for ssl Dec 03 15:14:10 mymachine start_apisix.sh[295]: stack traceback: Dec 03 15:14:10 mymachine start_apisix.sh[295]: [C]: in function 'error' Dec 03 15:14:10 mymachine start_apisix.sh[295]: ./bin/apisix:255: in upvalue 'init' Dec 03 15:14:10 mymachine start_apisix.sh[295]: ./bin/apisix:363: in field '?' Dec 03 15:14:10 mymachine start_apisix.sh[295]: ./bin/apisix:418: in main chunk Dec 03 15:14:10 mymachine start_apisix.sh[295]: [C]: in ? Dec 03 15:14:11 mymachine systemd[1]: apisix.service: Main process exited, code=exited, status=1/FAILURE Dec 03 15:14:11 mymachine systemd[1]: apisix.service: Failed with result 'exit-code'. ``` With 2.0, my `config.conf` contained ``` ssl: enable: true ``` and I could simply follow the "https guide": https://github.com/apache/apisix/blob/master/doc/https.md using the certs for my domain from letsencrypt. This does not work any more with 2.1. How can I enable ssl for the ssl `listen_port` for my domain name now? Is it still possible to enable https via the described method without having keys/certs locally in a folder before starting apisix? If not, may I suggest to add the required steps to https://github.com/apache/apisix/blob/master/doc/https.md . Also, does the message " lua: ./bin/apisix:255: missing ssl cert for ssl" refer to certs for encrypting to other services like etcd, or does it refer to ssl certs used for serving on port 9443? Meanwhile I downgraded to 2.0 and it works. Thanks a lot for your help! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
