Framework: PusherBroadcaster.php error from null socket

Created on 3 Jun 2018 · 11Comments · Source: laravel/framework

Laravel Version: v5.6.24
PHP Version: 7.2.1
Database Driver & Version:
pusher/pusher-php-server v3.0.4

Description:

I get this error from a message submit. The message appears into the chat window, even after refresh, but every message submit returns this http:500 error.

The pusher api configs are all in the .env

Steps To Reproduce:

Follow this tutorial:
https://pusher.com/tutorials/chat-laravel/

"message": "",
"exception": "Illuminate\\Broadcasting\\BroadcastException",
"file": "laravel\\vendor\\laravel\\framework\\src\\Illuminate\\Broadcasting\\Broadcasters\\PusherBroadcaster.php",
"line": 116,
"trace": [
    {
        "file": "laravel\\vendor\\laravel\\framework\\src\\Illuminate\\Broadcasting\\BroadcastEvent.php",
        "line": 48,
        "function": "broadcast",
        "class": "Illuminate\\Broadcasting\\Broadcasters\\PusherBroadcaster",
        "type": "->"
    },
    {
        "function": "handle",
        "class": "Illuminate\\Broadcasting\\BroadcastEvent",
        "type": "->"
    },
    {
        "file": "laravel\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\BoundMethod.php",
        "line": 29,
        "function": "call_user_func_array"
    },

Source

pursehouse

All 11 comments

@tillkruss no info? just closing it?

pursehouse on 3 Jun 2018

Yes, please read the info when opening a new issue.

tillkruss on 3 Jun 2018

👎1

The internals break and it doesn't even know why it broke itself. You don't think that's something to be fixed?

pursehouse on 3 Jun 2018

I have this exact same issue. Any resovle on this?

West1144 on 7 Jun 2018

@West1144 no, lemme know if you solve it though. Seems odd that the laravel people refuse to even let a ticket exist to fix their own code that breaks with no details of why it broke

pursehouse on 7 Jun 2018

New issues come with a template that must be filled in properly before anyone can even begin to help track down and fix possible bugs.

The Laravel team needs to know your Laravel version, PHP version, DB version (if applicable) and a set of steps that can be used to reproduce the bug on a clean install of Laravel. Also, what third part packages are relevant, if any?

Just pasting a stacktrace by itself doesn't help much. The official response was "please read the info when opening a new issue".