Sign In Sign Up

Quick Start Guide

Notta Socket is a drop-in replacement for Pusher and Laravel Reverb. This means you can use the official libraries you already know, just by pointing them to our infrastructure.

Configuration Reference

Use these settings to configure your client (Frontend) and server (Backend) libraries.

Setting
Value
Host
nottasocket.io
Port
443
Scheme
https
or
wss
Cluster
null
Force TLS
true
App ID, Key and Secret
Streams
Your Stream
Keys
Clustering is automatically handled. All requests to port
80
are redirected to port
443
for secured connection via SSL/TLS.
Supported Libraries

You don't need a custom SDK. Use the battle-tested libraries maintained by the community.

Frontend (Client-Side)

Backend (Server-Side)

Authentication & Private Channels

To use Private or Presence channels, your client must authenticate with your backend. You should not need to change your code. Since Notta Socket is API-compatible, your existing auth routes (e.g., Laravel's /broadcasting/auth) work automatically.

  • Ensure your backend is configured with your Notta Socket App Credentials.
  • Your backend will sign the auth request using our credentials, just like it would for Pusher.
Feature Support Matrix

Check the table below to see which protocol features are currently supported and what is coming next.

Feature
Status
Notes
Public Channels
Supported
Standard broadcast channels.
Private Channels
Supported
Requires backend authentication.
Presence Channels
Supported
Track who is online (member lists).
Client Events
Supported
Client-to-client messaging (e.g., "typing" indicators). Enabled by default.
Webhooks
Coming Soon
HTTP callbacks for channel occupancy.
Troubleshooting

If you're seeing errors in your console or server logs, check these status codes to identify the root cause quickly.

Error 4004: Connection Limit Reached

  • Cause: Your application has exceeded the maximum concurrent connections allowed by your current plan.
  • Solution: Upgrade your plan or close unused connections.

Error 401: Unauthorized

  • Cause: The credentials or settings used by your backend to sign the auth request does not match the ones in your Notta Socket stream.
  • Solution: Double-check your .env file and restart your queue workers.

Connection Refused / Timeouts

  • Cause: Often caused by firewall issues or incorrect port settings.
  • Solution: Ensure you are forcing TLS (useTLS: true) and using port 443.
Need Help?
If you're stuck, email us at support@nottasocket.com. We're developers too, so we'll get you sorted fast.

Ready to ship?

Stop wrestling with infrastructure. Start streaming real-time data in minutes.

Create Account