wpsignal

WordSocket sends realtime events from your WordPress site to connected browsers. 
When content changes: a post is published, a comment is approved, an option is updated: the plugin pushes the event to subscribers instantly via WebSocket (with SSE fallback).
On WordPress 7.0+, WordSocket also registers as a WebSocket-based Yjs sync provider for real-time collaborative editing in the block editor, replacing the default HTTP polling transport with a low-latency WebSocket connection.
Features:
<ul>
<li>One-click automatic connection via the WPSignal dashboard (no API key required)</li>
<li>Manual connection via API key for advanced setups</li>
<li>Disconnect button with inline confirmation, removes the site from the server immediately</li>
<li>WebSocket-first with automatic SSE fallback</li>
<li>Per-site JWT signing secrets: each site’s connection tokens are cryptographically isolated</li>
<li>AES-256-GCM encrypted event payloads: the WPSignal relay receives ciphertext only and never has access to plaintext message content</li>
<li>Real-time collaborative editing in the block editor (WordPress 7.0+, via Yjs sync provider)</li>
<li>Admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling</li>
<li>Built-in triggers for post updates and custom post types</li>
<li>Custom trigger builder: map any WordPress action hook to a realtime event</li>
<li>Public JavaScript API (<code>window.WPS</code>) for themes and plugins to share the connection</li>
<li>Extensible connection token: <code>wpsignal_token_channels</code> and <code>wpsignal_token_channel_prefixes</code> filters let other plugins add channels and namespace permissions to the JWT without modifying core</li>
<li>Admin explorer page with live event log, publish form, and token inspector</li>
<li>Short-lived JWTs (5 min) with automatic refresh</li>
</ul>
How it works:
<ol>
<li>Install the plugin and connect to the WPSignal service.</li>
<li>When content changes in WordPress, the plugin encrypts and publishes an HMAC-signed event to the WPSignal server.</li>
<li>The server pushes the ciphertext to all browsers subscribed to that channel.</li>
<li>The browser decrypts the payload and dispatches <code>wpsignal:*</code> DOM events. The relay never sees plaintext content.</li>
<li>On WordPress 7.0+, the block editor uses the same WebSocket connection for collaborative editing with no extra configuration.</li>
</ol>
<h4>Third-Party Service</h4>
This plugin connects to the WPSignal service at api.wpsignal.io for the following operations:
<ul>
<li>Site registration: when you connect in the admin (via the automatic one-click flow or by entering an API key manually), the plugin registers your site with the server and receives credentials.</li>
<li>Event publishing: when a trigger fires (e.g. a post is saved), the plugin sends an encrypted, HMAC-signed HTTP request to the server.</li>
<li>Realtime connections: logged-in users’ browsers connect to the server via WebSocket or SSE to receive events.</li>
<li>Collaborative editing: on WordPress 7.0+, Yjs document updates are relayed over the same WebSocket connection.</li>
</ul>
Event payloads are AES-256-GCM encrypted before leaving WordPress. The WPSignal server relays ciphertext and never has access to plaintext message content. Data is delivered in realtime and is not persisted on the server.
<ul>
<li><a href="https://wpsignal.io/terms" rel="nofollow ugc">Terms of Service</a></li>
<li><a href="https://wpsignal.io/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>

WordSocket

WordSocket is the official WordPress plugin for WPSignal (wpsignal.io), a third-party WebSocket/SSE delivery service.

Sergey Ivanov

NS Chat Plugin enables real-time communication between WordPress users using WebSocket technology, powered by the Workerman library.
Key Features: 
* Real-time private chat between users 
* Visual unread message indicators 
* Persistent chat history stored in the database 
* Lightweight modular JS + PHP architecture 
* Automatic migration and sync of WP users to chat system 
* Linux daemon service with SSL support for secure connections 
* Future-ready integration with NFS or AWS S3 for file upload/download
Planned Features: 
* Message editing and deletion 
* Read receipt indicators (message seen) 
* File attachments with optional NFS or AWS S3 integration
Ideal for community websites, intranets, or any platform requiring internal messaging without third-party services.
For integration help or consulting on adapting the plugin to your project, contact the developer at: ns.group.tech@gmail.com
<h3>WebSocket Server Setup (Linux with SSL)</h3>
<ol>
<li>
Create a systemd service file: 
<code>bash 
sudo vim /etc/systemd/system/websocket_server.service</code>
</li>
<li>
Paste the following content: 
<code>bash 
[Unit] 
Description=WebSocket Server for NS Chat (SSL) 
After=network.target 
[Service] 
ExecStart=/usr/bin/php /file/to/path/yourdomain/wp-content/plugins/ns-chat/server.php start 
Restart=always 
RestartSec=25 
User=www-data 
Group=www-data 
StandardOutput=file:/var/log/websocket_server.out.log 
StandardError=file:/var/log/websocket_server.err.log 
[Install] 
WantedBy=multi-user.target</code>
</li>
<li>
Add SSL context in <code>server.php</code>: 
<code>php 
$context = [ 
'ssl' => [ 
 'local_cert' => '/path/to/file.crt', 
 'local_pk' => '/path/to/file.key', 
 'verify_peer' => false, 
] 
];</code>
</li>
<li>
Set permissions for plugin folder: 
<code>bash 
sudo chown -R www-data:www-data /path/to/ns-chat/ 
sudo chmod -R 775 /path/to/ns-chat/</code>
</li>
<li>
Reload and start the daemon: 
<code>bash 
sudo systemctl daemon-reload 
sudo systemctl enable websocket_server --now 
sudo systemctl restart websocket_server 
sudo systemctl status websocket_server</code>
</li>
<li>
Check logs if needed: 
<code>bash 
/var/log/websocket_server.out.log 
/var/log/websocket_server.err.log</code>
</li>
</ol>
<h3>Custom Port Configuration</h3>
By default, the WebSocket server listens on port 2346.
To use a different port:
<ol>
<li>Change the port in <code>server.php</code>: 
<code>php 
$wsWorker = new Worker('websocket://0.0.0.0:2346', $context);</code></li>
<li>
Change the port in <code>ns-chat.php</code>: 
<code>php 
$ws_port = 2346;</code>
</li>
<li>
You can check and change the port in <code>chat-ui.js</code>: 
<code>js 
const port = nschat_data.wsPort || 2346;</code>
</li>
<li>
If the port is closed, then open a new port on your server’s firewall: 
<code>bash 
sudo ufw allow <your-port>/tcp 
sudo firewall-cmd --permanent --add-port=<your-port>/tcp 
sudo firewall-cmd --reload 
sudo iptables -A INPUT -p tcp --dport <your-port> -j ACCEPT 
sudo iptables-save > /etc/iptables/rules.v4</code>
</li>
</ol>
<h3>Database Tables</h3>
The plugin creates and uses the following tables:
<ul>
<li><code>wp_ns_chat_dialogues</code></li>
<li><code>wp_ns_chat_messages</code></li>
<li><code>wp_ns_chat_users</code></li>
</ul>
Tables are created and populated automatically on plugin activation.
<h3>User Synchronization</h3>
<ol>
<li>Initial migration of all users from <code>wp_users</code> to <code>wp_ns_chat_users</code> on plugin activation.</li>
<li>New registrations are handled by: 
<code>php 
add_action('user_register', 'ns_chat_add_user_on_registration');</code></li>
<li>Profile updates are synced via: 
<code>php 
add_action('profile_update', 'ns_chat_update_user_data');</code> 
You may bind these functions to custom hooks based on your app’s logic.</li>
</ol>
<h3>License</h3>
GPLv2 or later

NS Chat

Real-time WebSocket chat for WordPress with user sync and message history.

WordSocket vs NS Chat