Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I managed to get Pusher working on my local machines. I'm using Laravel 11, and I've built the project, pushed it to Git, and deployed it to Forge. However, when I post something on my app, I don't see any API messages from Pusher in the debugger, even though it connects to my private channels just fine. Is there a step I am missing I have noticed that .env called "PUSHER_HOST=" makes me wonder if I need to use it since I haven't during development.
I was using php artisan queue:work in my local for pusher. On forge I have configured a daemon to do that for me and it appears fine. In my laravel log I do see I am pushing data to my database fine as well although a new section in the json "socket = null" appeared which I haven't seen in my own dev environment.
Just need a push in the right direction.
Thank you.
I was having trouble with this as well, I just solved it by creating a queue worker, with the “Queue” link on the left side of forge I left the queue set to “default” but I changed the connection from “redis” to “database” and it started working
@soccerob So you are saying when you created your Queue worker you changed your connection from redis to database is that in your .env or is that when you are creating daemon?
Yeah, so the way I did it was that in Forge I started a daemon and told it where it should run. I used the command PHP artisan queue:work. Then within my application site on Forge, I selected "queue" and within that I wrote out the names of my workers. When I started this the first time I used default. If you are using default then remove Redis. In my case, I had Redis setup so I picked that.
Please or to participate in this conversation.