{"id":43845,"date":"2024-06-12T10:28:32","date_gmt":"2024-06-12T10:28:32","guid":{"rendered":"https:\/\/accuweb.cloud\/resource\/?post_type=faq&p=43845"},"modified":"2026-02-18T13:07:32","modified_gmt":"2026-02-18T13:07:32","slug":"websockets-support-for-php","status":"publish","type":"faq","link":"https:\/\/accuweb.cloud\/resource\/articles\/websockets-support-for-php","title":{"rendered":"Websockets Support for Apache & NGINX"},"content":{"rendered":"

Websockets Support for Apache & NGINX<\/h2>\n

WebSocket technology is a widely used method for instant messaging between a client and server within an application. It establishes a continuous, two-way communication link over TCP, resulting in minimal latency and rapid interaction. This technology can also traverse proxies and firewalls efficiently.<\/p>\n

Our platform offers robust WebSocket support by integrating it with the Shared Load Balancer<\/a> and NGINX balancer node. This allows you to use WebSocket features even without an external IP address, by consolidating various WebSocket app ports into a single port (80 for HTTP and 443 for HTTPS).<\/p>\n

The simplest way to set up WebSocket support for your application is by using an NGINX balancer (see detailed instructions in our documentation).<\/p>\n

However, if this approach doesn’t meet your needs, the platform fully supports WebSockets on available application servers like Apache (for PHP, Ruby, and Python<\/a> apps) and NGINX (for PHP<\/a> and Ruby<\/a> apps).<\/p>\n

The process of integrating WebSockets can vary depending on your application. We provide configuration samples for each of these server nodes, making it easy to enable WebSocket support by uncommenting and adjusting a few settings, such as the listener port number, to fit your app’s requirements.<\/p>\n

In the step-by-step tutorial below, we’ll demonstrate an example of configuring WebSockets for a simple PHP chat project deployed without a balancer server, utilizing WebSocket technology. Let’s begin from the start.<\/p>\n

Create an Environment and Deploy the Application<\/h2>\n

Using the platform, you can easily create the environment<\/a> you need in just a few clicks. Simply log into your PaaS account and follow these steps:<\/p>\n

Step 1.<\/strong> Click the “New Environment<\/strong>” button located in the top left corner of the dashboard.<\/p>\n

\"New<\/a><\/p>\n

Step 2.<\/strong>\u00a0In the Environment Wizard window that appears, navigate to the tab for your chosen programming language. Select the desired application server (for our example, we’ll use Apache<\/strong> to serve our PHP application). Use the cloudlet<\/a> sliders to allocate the necessary resources. Enter a name for your environment (e.g., apache-WebSockets) and then click “Create<\/strong>.”<\/p>\n

\"Environment<\/a><\/p>\n

Step 3.<\/strong>\u00a0Your new environment will appear on the dashboard in a few minutes.<\/p>\n

\"Creating<\/a><\/p>\n

Step 4.<\/strong> Upload and deploy your application using the platform’s Deployment Manager or through a remote GIT\/SVN repository. Detailed instructions for deploying based on your chosen engine can be found in our Deployment Guide.<\/p>\n

\"Created<\/a><\/p>\n

As a result, your deployed project will appear in the corresponding section within the environment’s panel.<\/p>\n

Server and Application Configurations<\/h2>\n

WebSocket support in the Apache server is enabled through the proxy_wstunnel_module module, which is included in the default server build. NGINX, on the other hand, can proxy WebSocket connections directly within the application server, similar to how NGINX-balancer operates.<\/p>\n

Now, let’s configure your application server.<\/p>\n

Step 1.<\/strong> Click the “Config<\/a>” button next to your application server node.<\/p>\n

\"Config\"<\/a><\/p>\n

Step 2.<\/strong> In the Configuration Manager tab that opens, follow the steps in one of the instruction sections based on your chosen server:<\/p>\n

<\/div>\n\t\t
\n\t\t\t
\n \n
\n
\n
\n \n \t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n
<\/div>\n

For Apache application server<\/h3>\n

Locate the `httpd.conf<\/strong>` file in the `conf<\/strong>` directory and uncomment the specific lines at the end of the file (around line 962).<\/p>\n

\r\n<Location \/ws>\r\nProxyPass ws:\/\/127.0.0.1:<PORT>\r\nProxyPassReverse ws:\/\/127.0.0.1:<PORT>\r\n<\/Location><\/code><\/pre>\n
<\/div>\n
Now, update both parameters to match the port number used by your WebSocket application (for example, ours uses port 9000).<\/p>\n
Ensure that it matches the configuration shown in the image below.<\/p>\n
\"Configuration<\/a><\/p>\n
Save the changes by clicking the button labeled with the same name above the editor.<\/p>\n
For NGINX application server<\/h3>\n
Locate the `nginx.conf<\/strong>` file in the `conf<\/strong>` directory and uncomment the specific lines in the “#Websocket support” section.<\/p>\n
\r\nupstream websocket {\r\nserver 127.0.0.1:<PORT>;\r\n}\r\n&hellip;\r\nlocation \/ws {\r\nproxy_pass http:\/\/websocket;\r\nproxy_http_version 1.1;\r\nproxy_set_header Upgrade $http_upgrade;\r\nproxy_set_header Connection \"Upgrade\";\r\n}<\/code><\/pre>\n
<\/div>\n
Next, replace the `<PORT><\/strong>` placeholder with the actual port number used by your WebSocket application, and then save the changes you made.<\/p>\n
\"Change<\/a><\/p>\n
Step 3.<\/strong> That’s all the server configurations you need to complete. Now, configure your deployed application by accessing its configuration file responsible for WebSocket settings. Adjust the `ws` path within the file to follow this format:<\/p>\n
```\r\nws:\/\/{env_domain}{path_to_ws_file}\r\n```<\/code><\/pre>\n
Here’s what each part should be replaced with:<\/p>\n