Can you expand on your request a little bit? I don't think that there is something complicated in database notifications there :)

.env file is missing configurations... for whatever reason installation only added to real .env file and not into example!

I will update them in the morning (or you can find them by running the install command again)

I'll have to try again tomorrow - appear to have sorted the .env now by added the reverb env entries however now I seem to have this constantly in my Chrome browser console, I presume my local setup may require tweaking... I am using Herd currently (e.g all my dev urls end in .test)

GET http://127.0.0.1:5173/ net::ERR_CONNECTION_REFUSED

This seems okay! It probably does not match the port in the .env file ( tho I did not test it on herd )

Weirdly it seems to be all connected now in the WS tab in Chrome but running the artisan commands did nothing... i'll wait for the updated repo and hopefully someone one using Herd can point me in the right direction

Hey, updated the repository to have .env.example filled with values that worked on my end! Hopefully this works (and you can compare it with what you put on!)

Hi, no, if you don't use queues. Change your .env driver from redis to sync and it should start working again

Thank you very much for your response.

Hi. It's better if you put this in the content course because Laravel 11 comes with QUEUE_CONNECTION=database by default. It took me a while fixed it.

Cheers.

did you guys manage to get this working for you?

Have you launched reverb and a queue worker?

Not sure if I'm doing it right, but here's what I did:

• php artisan serve
• php artisan reverb:start
• php artisan queue:work
• php artisan system:notify-maintenance (and proceeded to enter a future date)

could you run:

php artisan reverb:start --debug

and see what it outputs?

also, please check browser networks "ws" tab to see if it connected to sockets

Running php artisan reverb:start --debug outputs this:

{
    "event": "SystemMaintenanceEvent",
    "data": {
        "time": "2024-07-03"
    },
    "channel": "system-maintenance"
}

The ws Messages:

channel: "system-maintenance"
data: "{\"time\":\"2024-07-03\"}"
event: "SystemMaintenanceEvent"```
 
Request URL:
ws://127.0.0.1:8080/app/vsthk74otyhwvr62kvka?protocol=7&client=js&version=8.4.0-rc2&flash=false
Request Method:
GET
Status Code:
101 Switching Protocols

It seems that the event is triggered and ws message is retrieved... but now I wonder why it did not update on the UI for you. There was no console logs for any error? Or maybe you have an adblocker running?

console.log(event) yielded nothing. No adblockers and even turned off firewall.

Hmm, this is weird. Last question then:

Is your .env configured correctly with the REVERB variables? If they are and you still need help - feel free to email us (mark in the email that it should be forwarded to Modestas) and I'll assist you there as much as I can :) (ps. Same can be done in our discord!)

dis you compile your assets?

Yes, new laravel installation,

1. npm run build
2. php artisan serve

I would check that echo.js is loaded in the website assets and is correctly included

That wasn't what I was referring to, but also check if everything is wrapped in:

window.addEventListener('DOMContentLoaded', function () { ... })

Because this is important.

Okay, did you install the broadcasting package?

Yes i followed all steps and also run php artisan reverb:start

finally the error was i didnt have the following on head @vite(['resources/css/app.css', 'resources/js/app.js'])

But i see another error in console now wss://localhost:8080/app/3jxinlvwqfw6zd6q929e?protocol=7&client=js&version=8.4.0-rc2&flash=false failed: WebSocket is closed before the connection is established.

i get all the same problems

hy giuys have you solved the issue of reverb?

Sorry, the formatting of the message is a bit messed up...

1. Ping is not the event you should see in the log. You should see your own named event there in order for it to work
2. There is some kind of an error, hard to say what.
3. To get the configuration - you have to fill it yourself or run the php artisan broadcasting:install command.

As for why the UI would not update - as soon as you see the correctly named event apear in your WS console - you should see UI update. If that's not the case, check for js errors in browser console

I clonning the repo from github with regenerate key and install Composer at first and cp .env ...and all of this why the reverb not working and before use reverb also pusher was not working !!

Yes, but our .env.example does not have all values filled for the REVERB configuration, so they should be configured as needed :)

But if you also had issues with pusher before - then there might be something else wrong. Like a port being blocked or something else like that

I am sorry for many comments but I want to show you the new error i get at console , WebSocket connection to 'ws://localhost:8080/app/3prtjfbbgn54t6w8diu0?protocol=7&client=js&version=8.4.0-rc2&flash=false' failed:

If you have any ideas or solutions , thanks for laravel daily team

if anyone manages to get around the problems please let me know ❤️

This error message can mean A LOT of different things sadly, so it's hard to say what is happening there.

But from what I've learned:

If you are using docker/WSL2/windows setup - the whole reverb thing can become really tricky to get working. And sadly, I we don't have the solution for these problems... What I can suggest is - taking the whole setup from scratch and doing it like it's written in the documentation. Then adding the parts that are missing from our tutorial :) That sometimes helps people

After some trial and erros I managed to do it, I hope it will be helpful to someone else

 $title = $data['title'];
 $message = $data['message'];
 $url = $data['url'];
 $user = User::find($data['user_id']);
 
 Notification::make()
 ->success()
 ->title($title)
 ->body($message)
 //->persistent()
 ->actions([
     Action::make('View')
         ->button()
         ->url($url, shouldOpenInNewTab: true),
 ])
 ->broadcast($user)
//queue:listen or queue:work should be running so that the notification will be displayed under the notifications modal panel (Bell Icon)
 ->sendToDatabase($user)
 ->send();
 // use instead of database polling
 event(new DatabaseNotificationsSent($user));

Hmm, it should not be impacted by the connection.

When creating this article, I've tested the logging in/out workflows quite a few times and did not see an issue with this...

Have you tried running reverb in debug mode? Does it show the event?

I'm not sure what the issue is here. This seems normal, since as soon as you subscribe to a channel - this message should pop up.

and I run it with the command

1. php artisan reverb:start
2. 2. php artisan queue:listen
3. 3. php artisan system:notify-maintenance the message still can't be sent but when I match the port I use in the application and reverb, the message is can be sent. My application is on port 81 and reverb is on port 8080, I equalize the reverb port on 81, messages can be sent but my application can't be opened. is there another setting I'm missing?

app and reverb should be running on separate ports.

You could check network tab for any issues with wss connection

it is now up and running, i am using nginx and nginx.conf i added /ws to location location /ws { proxy_pass http://localhost:6001; # Change to your WebSocket server address proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; }

Your broadcast driver is:

BROADCAST_DRIVER=log

Try to change that to reverb

Thank you for getting back to me fast, I've changed that.

Ran npm run build, then restarted reverb: php artisan reverb:start --debug and re-ran the code again:

php artisan system:notify-maintenance
 
 When should it happen?:
 > 20:00

And nothing but in the safari browser inspect element it's moaning about these: You must pass your app key when you instantiate Pusher. on app.js

And this bit on your code for the layouts to show the event:

TypeError: undefined is not an object (evaluating 'window.Echo.channel')

Which is on:

window.Echo.channel('system-maintenance')

Thank you for your help.

It seems that it's trying to launch pusher at this point. Which is not really what you are trying to do here.

Check that:

• You have correct .env information filled
• That you deploy that information (for example, you haven't cached wrong .env values)

But honestly, it's really hard to try and debug this via comments. Often it's some small value misconfigured :)

Thanks mate,

I tried to remove Pusher but got this: laravel/reverb v1.4.8 requires pusher/pusher-php-server (^7.2)

So just removed the .env details relating to pusher, and edited the broadcasting to remove it by following the docs: https://laravel.com/docs/12.x/broadcasting#pusher-channels

Didn't fix anything but thank you for your help I need to dive into this more as it's a pain in the bum haha.

Oh no, I did not mean to remove it - more to check that no settings use it!

For faster debugging - launch a new project with reverb (fresh laravel), check the configs and see the differences :)

Thank you, I created a new app, followed the basics of the tutorial on Laravel 12, to the bit where it should echo a date in like a var_dump.

And I don't get that, I get an error message about the channel.

Thanks for your help mate.

This seems that Echo wasn't correctly registered/loaded in the app.js file. Or it wasn't included in your template - check that :)

thank you for your fast reply mate, this is what i have in my resources/js/app.js

Did you compile the assets with 'npm run build'? And did you include the compiled js files into your app?

ps. Compiling assets - saves the keys in js files. So any changes to config and you have to re-compile

npm run build mate?

Yes! You have to compile the assets with nom so that they would be used :)

Unless you had something else in mind?

yeah i run that alot to rebuild any changes. but it didn't fix it, weirdly i'm using the livewire starter kit.

It doesnt matter which kit, since they all use same logic :)

But that is still weird...

so confused haha

Can you provide what issues you got while doing everything from this youtube video? As you said configuration can vary for every server so it's impossible to write about each case.