Can't connect to soketi and pusher on sail. | Laravel | Page 1

slow bay Feb 8, 2024, 7:30 PM

#

Hi this is my first time using soketi, and i'm running sail. I made a pusher app on the pusher website and i'm trying to make a chat.
I always get this error : WebSocket connection to 'wss://soketi:6001/app/app-key?protocol=7&client=js&version=4.3.1&flash=false' failed.

here's my .env

PUSHER_APP_ID=app-id
PUSHER_APP_KEY=app-key
PUSHER_APP_SECRET=app-secret
PUSHER_HOST=soketi
PUSHER_PORT=6001
PUSHER_SCHEME=http
PUSHER_APP_CLUSTER=eu```

here's my bootstrap.js 
```window.Echo = new Echo({
    broadcaster: 'pusher',
    key: import.meta.env.VITE_PUSHER_APP_KEY,
    cluster: import.meta.env.VITE_PUSHER_APP_CLUSTER ?? 'eu',
    wsHost: import.meta.env.VITE_PUSHER_HOST ? import.meta.env.VITE_PUSHER_HOST : `127.0.0.1`,
    //wsHost: `localhost`,
    wsPort: import.meta.env.VITE_PUSHER_PORT ?? 6001,
    wssPort: import.meta.env.VITE_PUSHER_PORT ?? 6001,
    forceTLS: (import.meta.env.VITE_PUSHER_SCHEME ?? 'http') === 'http',
    enabledTransports: ['ws', 'wss'],
    forceTLS: false,
    encrypted: true,
    disableStats: true,
});```

if i try as host, localhost or 127.0.0.1 i get the same error.
if i try to send a message i get this error: 
```Pusher error: cURL error 52: Empty reply from server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://soketi:9601/apps/app-id/events?auth_key=app-key&auth_timestamp=1707420501&auth_version=1.0&body_md5=e157b1ede56a457048297133d7dd4dcf&auth_signature=5836d9e3d15e4f5b0ce8b0a44b3a3272ba65550543f1f0a513b345173cff706f```

I have of course set app-key app-id and app-secret.

thank you!

#

Can't connect to soketi and pusher on sail.

uncut sedge Feb 9, 2024, 3:21 AM

#

soketi and the pusher website are two different things

#

If you've gone down the soketi route, then you'll need to replace the variables app-id, app-key, app-secret with what you've configured in soketi

BROADCAST_DRIVER=pusher
PUSHER_APP_ID=app-id
PUSHER_APP_KEY=app-key
PUSHER_APP_SECRET=app-secret
PUSHER_HOST=soketi
PUSHER_PORT=6001
PUSHER_SCHEME=http
PUSHER_APP_CLUSTER=eu

#

the Pusher website is if you don't want to use soketi, and instead want to use the Pusher app
Otherwise, soketi "speaks" the same as Pusher, so if you want to self-host, then you just need to configure your soketi server appropriately

slow bay Feb 10, 2024, 12:06 PM

#

thank you i never tought of that. i'll try

slow bay Feb 10, 2024, 12:56 PM

#

Is there any best practice on how to configure it on sail?

slow bay Feb 10, 2024, 2:02 PM

#

Ok i did configure it but it keeps failing. i tried with localhost and 127.0.0.1 and it gives this warining failed: WebSocket is closed before the connection is established. and then WebSocket connection to 'wss://localhost:6001/app/85007e4a489a74a21006?protocol=7&client=js&version=4.3.1&flash=false' failed: and if i use as host the name of the container, so "soketi" ti only gives me WebSocket connection to 'wss://soketi:6001/app/85007e4a489a74a21006?protocol=7&client=js&version=4.3.1&flash=false' failed: error.

#

I did change the soketi vars

#

on the soketi docker logs i get nothing, is blank, even if i try to connect to it.

uncut sedge Feb 14, 2024, 8:08 AM

#

Does your browser have access to that port? Is it piped through to soketi? It looks like your browser cannot connect to your Soketi instance

potent tree Feb 14, 2024, 12:08 PM

#

What does your docker-compose file for sail look like? Maybe there are missing port bindings.

slow bay Feb 14, 2024, 2:16 PM

#

uncut sedge Does your browser have access to that port? Is it piped through to soketi? It ...

is there any way i can test it using postman?

slow bay Feb 14, 2024, 2:16 PM

#

potent tree What does your docker-compose file for sail look like? Maybe there are missing p...

here's my docker compose

📎 message.txt

#

i really cant find something wrong

potent tree Feb 14, 2024, 3:05 PM

#

Okay hm looks like mine.

You set all env variables for vite with the prefix VITE_ for it?
Example:

VITE_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
VITE_PUSHER_HOST="${PUSHER_HOST}"
VITE_PUSHER_PORT="${PUSHER_PORT}"
VITE_PUSHER_SCHEME="${PUSHER_SCHEME}"
VITE_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

Your backend has to connect to soketi and your frontend has to connect to localhost:6001. You could check if http://localhost:9601/ returns OK inside your browser.
Is docker showing the mapped ports with docker ps or a similar command?

slow bay Feb 14, 2024, 4:23 PM

#

yes the env var are correct.

#

localhost 9601 returns ok and dockers shows mapped ports

uncut sedge Feb 15, 2024, 5:45 PM

#

slow bay localhost 9601 returns ok and dockers shows mapped ports

In your browser, does soketi:9601 return "ok"?

#

Or does localhost:9601?

#

or both?

slow bay Feb 16, 2024, 10:28 AM

#

yes both

uncut sedge Feb 18, 2024, 2:15 AM

#

It's likely to be down to the correct protocols not being in place/configured

#

Where I'm using Soketi, I have various things in front of it (e.g. CloudFlare, an Nginx Proxy), so my setup probably won't help you much

#

If you can provide the headers that your browser is sending, then that'll help point me in the right direction

What does your Soketi console say when a connection attempt happens?

slow bay Feb 19, 2024, 11:42 AM

#

Sorry for the late reply but i wasn't home. The log from the soketi console (it is a bit long so it will be a txt)

📎 message.txt

uncut sedge Feb 19, 2024, 10:42 PM

#

So if you see this bit here:

        type: 'AuthError',
        error: 'The connection is unauthorized.',
        status: 401

#

You haven't defined your auth callback etc

#

You need to configure that bit, so that when Soketi makes the callback, it knows if the user is authorised or not

slow bay Feb 20, 2024, 9:53 AM

#

how do i do it?

#

So, reading the soketi and pusher documentation it appears that the user needs to be authenticated to the app. My users are authenticated to the app

#

/*
|--------------------------------------------------------------------------
| Broadcast Channels
|--------------------------------------------------------------------------
|
| Here you may register all of the event broadcasting channels that your
| application supports. The given channel authorization callbacks are
| used to check if an authenticated user can listen to the channel.
|
*/
Broadcast::channel('newmessage', function ($user, $id) {
    return (int) $user->id === (int) $id;
});```

#

it is like this in channels.php

#

If return directly true, it happens the same error

slow bay Feb 20, 2024, 11:44 AM

#

ok now it's throwing POST http://localhost/broadcasting/auth 403 (Forbidden) this error.

slow bay Feb 20, 2024, 3:19 PM

#

i cloned my repo on another pc, installed the project and now it works fine

#

i don't know how

#

maybe it was a wrong or outdated soketi config

#

i'm sorry

#Can't connect to soketi and pusher on sail.