Hi, I'm trying OpenResty on ISPConfig. I've removed NGINX and installed OpenResty. First test: new site created, but no SSL certificate was acquired. I suspect the issue is OpenResty's executable name (openresty vs nginx). I'm thinking of addressing this with a symlink or custom service. Before spending more time testing solutions, I wanted to ask: Is this setup feasible in your opinion? What potential implications does replacing NGINX with OpenResty have? Thanks!
OpenResty is not tested to work with ISPConfig. So, creating a symlink to mimic the nginx binary may or may not work. It could be that the TLS 1.3 detection won't work with OpenResty but also that is untested and needs verification. Another thing you'll have to make sure is to use the nginx service instead of the one that comes with openresty. ISPConfig only knows the nginx system service unit. Maybe you can use systemctl --link (--user) <..> to create a link named nginx.service to the openresty service. Under the bottom line you'll have to test all these things on your own, but feel free to report your results!
I don't think that you can use OpenResty as a drop-in replacement for Nginx, so you will likely have to build a new ISPConfig server plugin for it based on the current Nginx plugins with separate templates etc.
