Since this issue is apparently out of scope of the OLS guides, I will have to study this issue further, maybe on other forums. But how I am going to "transfer" the AutoSSL capabilities from cPanel WHM (using Let's Encrypt) to work properly on OLS proxy is not clear. My idea is to use exactly the same SSL certificate I was using on Apache (which will be the backend and therefore not directly accessible from users - no need for SSL). Even though I can use expired/invalid certificate, it would be a bad idea to have website visitors getting warning messages on their web browsers due to bad certificate (I will stay using full encryption on Cloudflare). Thank you for your clarification, it wasn't clear for me (nor through OLS's documentation) that the certificate was strictly necessary on port 443.īut the SSL certificate choice is not trivial. So the issue is with the https listener that can't be enabled.Īny thoughts on what could be causing the issue with the https listener? How can I troubleshoot this? What I find strange is that, even when I changed the listener ports to unused ones, 30000 (http) and 30001 (https), to allow reverting apache to 80 and 443, the https listener still shows red (disconnected) in the admin dashboard. Also, in the server error log, I got 2 error messages (listed below), but I think they are related to configurations not being used, since there is really no listener named "default" (my 2 listeners are named "listener_http" and "listener_https"): From the dashboard of the LiteSpeed WebAdmin Console, my http listener appears green (connected), while the https listener appears red (disconnected). Unix 2 STREAM LISTENING 8352154 14665/openlitespeed /usr/local/lsws/cgid/cgid.sockSo it's clear that only proxy on port 80 is working as expected. Unix 2 STREAM LISTENING 8352148 14665/openlitespeed /usr/local/lsws/admin/tmp/admin.sock.7436 Website access returns error 521 (host down) Greaceful restart OLS and then through CLI systemctl restart lswsġ0. Checked it worked through CLI netstat -lnp | grep httpdĩ. Apache ports changed to 8098 (http) and 8099 (https) directly through cPanel's WHM. Assigned the 2 newly created listeners to my Virtual host through Virtual host mappings (domain name as domain.tld and virtual host name > assigned to my newly created virtual host)Ĩ. Created listener 2 > IP Address: ANY / port: 443 / secure: yesħ. Created listener 1 > IP Address: ANY / port: 80 / secure: noĦ. Inside this newly created Virtual host: Rewrite > Enable rewrite: yes / Autoload from. Virtual Host created > (Virtual host root (where wordpress installation is located): /home//public_html - Document root: $VH_ROOT)Ĥ. Server configuration > External App > Webserver 2 created: (name: apachehttps)ģ. Server configuration > External App > Webserver 1 created: (name: apachehttp)Ģ. I will mention the steps I took, if any of you could help on the troubleshooting, I would greatly appreciate.ġ. I get error 521 (host is down) when i try to visit the website (OLS configured as reverse proxy). I've already tried do configure OLS as reverse proxy some hours ago, but it didn't work. Since my knowledge is very limited, it seems to me that configuring OLS as reverse proxy is not much complicated (less things to go wrong due to misconfiguration). In a first experimentation with OpenLiteSpeed, I would still prefer to test the site with Cloudflare -> OLS -> Apache.
0 Comments
Leave a Reply. |