Error while use Soketi in production

[RabieAli95]

I just deployed Soketi on EC2 with all its things (SSL, config Nginx proxy and etc) and I got a response in my domain (OK) which returns from Soketi so I assume all things are just fine! the domain (realtime.my_doamin.co). I connected with the client side and the Network is:

On the server-side I got a weird error:

Pusher error:.

Full error: https://ibb.co/FJpnKs2

Here is the way I used it with Laravel:

in .env file

PUSHER_APP_KEY=app-key
PUSHER_APP_ID=app-id
PUSHER_APP_SECRET=app-secret
PUSHER_HOST=realtime.my_doamin.co
PUSHER_PORT=80

in bootstrap.js file:

window.Echo = new Echo({
    broadcaster: "pusher",
    key: "app-key",
    wsHost: "realtime.my_doamin.co",
    wsPort: 80,
    wssPort: 443,
    forceTLS: "https",
    enabledTransports: ["ws", "wss"],
});

window.Echo.channel("orders").listen("OrderStatusUpdated", (e) => {
    console.log(e);
});

In config/broadcasting.php file:

'pusher' => [
            'driver' => 'pusher',
            'key' => env('PUSHER_APP_KEY', 'app-key'),
            'secret' => env('PUSHER_APP_SECRET', 'app-secret'),
            'app_id' => env('PUSHER_APP_ID', 'app-id'),
            'options' => [
                'host' => env('PUSHER_HOST', '127.0.0.1'),
                'port' => env('PUSHER_PORT', 6001),
                'scheme' => env('PUSHER_SCHEME', 'http'),
                'encrypted' => true,
                'useTLS' => env('PUSHER_SCHEME', 'https') === 'https',
            ],
        ],

In OrderStatusUpdated.php file:

class OrderStatusUpdated implements ShouldBroadcast
{
    use Dispatchable, InteractsWithSockets, SerializesModels;

    public function __construct(public $id)
    {
    }

    public function broadcastOn()
    {
        return new Channel('orders');
    }
}

in web.php file:

class Order
{
    public function __construct(public $id)
    {
    }
}

Route::get('/', function () {
    return view('welcome');
});

Route::get('/test', function () {
    OrderStatusUpdated::dispatch(new Order(1));

    return 'Event has been sent!';
});

I think there is a problem with SSL on the server side in the Laravel project.

I used Certbot to install SSL for the Soketi server

Here in docs SSL I did not do anything like it! Should I?

[DarkGhostHunter]

Almost the same here. No error though.

Soketi works, Laravel pushes the event through one of the workers, but Soketi does not return it to the front end, like it never received something to push.

[RabieAli95]

@DarkGhostHunter Beside the above issue I've got the same issue with no receiving data in frontend!

[DarkGhostHunter]

I fixed it. It was using “app-secret”. Soketi received the payload, but didn’t push it because the secret was incorrect, even if the whole payload is correctly signed. Check with debug if there is a payload received by soketi. You may have your app secret wrong. Side note: all ENV keys for the soketi process must be appended with ”SOKETI_”, otherwise the process won’t pick them up. I learned the hard way using the docker installation. Italo Baeza C.

…

El 27-08-2022, a la(s) 05:01, RabieAli95 ***@***.***> escribió:  @DarkGhostHunter Beside the above issue I've got the same issue with no receiving data in frontend! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[RabieAli95]

@DarkGhostHunter NICE!
just a question pls, how did you install the SSL on your server? and is there anything I have to config with Soketi after installing SSL on the server?

I just installed SSL by Certbot I do not know whether this is the right or wrong way!

[RabieAli95]

@DarkGhostHunter How to check!

[DarkGhostHunter]

I'm using a load balancer / proxy in front. SSL config is in the documentation. From there your on your own, but as far as I remember certbot saves the SSL certificates and keys somewhere, you just have to find them. From there you're on your own. I recommend you investigate using a load balancer or proxy instead of manually configuring SSL for each app and domain, like Traefik or Caddy.

To debug Soketi you need to use SOKETI_DEBUG=1. The debug information will be shown on the process output, not on the WebSockets connection.

[RabieAli95]

@DarkGhostHunter Pls I got confused with config Soketi with SSL

I need to create a JSON config file and put these into the file

SOKETI_SSL_CERT
SOKETI_SSL_KEY
SOKETI_SSL_PASS
SOKETI_SSL_CA

then run soketi start --config=/path/to/config.json to that config. Is that right?

[DarkGhostHunter]

You may hire someone to do that for you if it seems too difficult to configure.