Let’s set up OpenLiteSpeed as a WebSocket Proxy with this article. As part of our Server Management Service, Bobcares provides answers to all of your questions.

OpenLiteSpeed as a WebSocket Proxy: Setup Steps

When using a WebSocket proxy, OpenLiteSpeed will route traffic to the WebSocket backend that the WebSocket proxy specifies along with the WebSocket upgrade request. An other Context can handle traffic in the absence of this upgrade request.

This implies that we may continue to use OpenLiteSpeed to handle connections efficiently and securely while keeping the WebSocket application behind it. It also implies that we may have WebSocket content on the same page as well as benefit from OpenLiteSpeed’s effective static or dynamic content solution.

The steps to set up OpenLiteSpeed as a WebSocket Proxy are as follows:

1. Setting up a functional WebSocket backend is the first step.

2. We will need to test the backend WebSocket to make sure it is operational, assuming it is up and running on port 7682 at ws://domain.com:7682.
Nowadays, many tools are available for this kind of testing.

3. Within the virtual host settings, we’ll find the WebSocket Proxy tab (WebAdmin console > Virtual Hosts > your virtual host > WebSocket Proxy > Add).

4. Input both the WebSocket backend address and the application’s URI.

5. The address value is 127.0.0.1:7682 if that is the port on which the backend server listens. We may set the backend and pages such that the WebSocket application is located in a separate URI and the backend is situated in a different place.

6. Lastly, open the browser and navigate to http://yourIP:8088. The WebSocket page should load and run flawlessly, with the virtual host on port 8088 and the actual application on port 80.

[Looking for a solution to another query? We are just a click away.]

Conclusion

This article briefly explains about the steps to set up OpenLiteSpeed as a WebSocket Proxy.