I need, in other words, a reverse proxy combination of both websockets and standard http addresses. I've done simple proxies before like this one, but never have I ever had to use websockets in OLS or a combination of websockets and http in OLS.
Update: I have been trying in vain to get Collabora set up in a reverse proxy and it keeps erroring out when I attempt to do so. As a temporary workaround, I can configure Collabora to be publically accessible via an SSL encrypted connection at port 9980 bypassing OpenLiteSpeed entirely, but I would greatly prefer a reverse proxy in OLS. Since OLS differs a bit from Apache or nginx and it does not have a straightforward way of configuring websockets in combination with a normal reverse proxy, I have hit an impasse at this point.
Thank you. That makes sense. How would I apply this in the context of CyberPanel? I have a site already defined for office.techandtiny.com and it already creates an external app which is located at UDS://tmp/lshttpd/officet.sock.
It does not, but I do have automated SSL (Let's Encrypt) renewals occur through their interface for the domain. So if I do this totally manually, there would no longer be panel-activated automated renewal for the SSL certs. If possible, I would prefer having my cake and eating it too.
Bingo! I almost gave up hope when I specified URI paths of "/lool/(.*)/ws$" and "/lool/adminws" for the two web sockets proxies to 127.0.0.1:9980 that Collabora recommends in their reverse proxy guides for Apache and ngnix--no dice. In act of frustration, I instead specified the URI path as simply "/" and the address as "127.0.0.1:9980" for a single web socket proxy. That works handedly! Solved!