pusher | A fast massive push platform for APNs and FCM | Pub Sub library

I updated laravel to version 8.

I have a problem when I run this method (with the migrate command):

I still have this problem after asking the same question here: JSON returned from auth endpoint was invalid, yet status code was 200 with no response. I've looked at similar questions and followed the suggestions: setting my broadcast driver to 'pusher', uncommenting 'App/BroadcastServiceProvider' class in my app.config file, setting debug mode to false in my .env file, etc. I have also looked at pusher docs but the issue remains unresolved for me.

I have updated my previous attempt by adding '/broadcasting/auth/' auth endpoint and headers but still the same error. But I can now see a 302 redirect to the auth route then a 302 redirect to the login route then to the dashboard with a 200 response on laravel telescope, which I wasn't seeing before now. So this suggests to me that adding the auth endpoint ought to resolve the issue but it doesn't.

I also tried setting up and using a '/pusher/auth/' auth end point route and controller but it gave me a 'Failed to load resource: the server responded with a status of 405 (Method Not Allowed)' along with "Error: Unable to retrieve auth string from auth endpoint - received status: 405 from /pusher/auth, but not the previous invalid json error. I get this with a 'get' request to the controller but a 500-internal server error with a 'post' request. I really don't know which is correct.

This is my bootstrap.js file:

I recently performed a rather large update to this web app, and for the most part it went off without a hitch... Until the app tries to send an SMS notification from staging/production.

The upgrade from laravel 7.x to 8.x was quite simple and straightforward. At the same time we also installed Laravel Horizon. Everything went according to plan, and all works fine locally.

When we deploy to staging/production however, queued SMS notifications fail with the following exception:

ReflectionException: Class Http\Adapter\Guzzle6\Client does not exist in /home/forge/dev.example.com/releases/20210609194554/vendor/laravel/framework/src/Illuminate/Container/Container.php:836

Looking in the stack trace we can see that Nexmo is the culprit:

#5 /home/forge/dev.example.com/releases/20210609194554/vendor/nexmo/laravel/src/NexmoServiceProvider.php(150): Illuminate\Foundation\Application->make()

However in our composer.json file we are requiring Guzzle 7 with the following:

"guzzlehttp/guzzle": "^7.3",

It is worth mentioning again at this point, I have no issues sending SMS locally, the main difference between local and staging environments is that locally I use Laravel Valet and Staging uses Laravel Envoyer.

What I've tried so far:

• Changing "guzzlehttp/guzzle": "^7.3" to "guzzlehttp/guzzle": "^6.5|^7.3"
• Running php artisan horizon:purge and php artisan horizon:terminate both manually and in a deployment hook.
• Restarting the laravel horizon daemon on forge.
• trying php artisan queue:restart
• running composer dump-autoload and composer dump-autoload -o
• deleting composer.lock and the vendor/ directory from current/ then running composer install
• Restarting PHP, Nginx, and eventually the entire server :(

and more...

Any help is greatly appreciated

UPDATE Below:

Complete composer.json:

We are implementing a custom chat in a web application using Laravel and pusher. The basic functionalities like sending and receiving messages with file-sharing were working perfectly fine for few days but all of a sudden we encountered an error as follows:

"message": "cURL error 60: SSL: no alternative certificate subject name matches target host name 'api-.pusher.com' (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://api-.pusher.com/apps//events?auth_key=&auth_timestamp=1622911129&auth_version=1.0&body_md5=994999b61168dbbbb9172e79341131b8&auth_signature=51992f8acbe3f6943163bb358399f30b7d8020d30a5d121e1650953480642397", "exception": "GuzzleHttp\Exception\RequestException", "file": "/home/techfin/public_html/testtest.com/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php", "line": 211

It works perfectly fine on the local machine but causes problems on the server.

The problem

For a Lumen 8 project we are trying to implement Pusher. We got it working locally in a Docker environment, but when we turn to Kubernetes it isn't working anymore. We get this error:

[2021-05-27 17:56:36] production.ERROR: Pusher error: 404 NOT FOUND {"exception":"[object] (Illuminate\\Broadcasting\\BroadcastException(code: 0): Pusher error: 404 NOT FOUND at /var/www/html/vendor/illuminate/broadcasting/Broadcasters/PusherBroadcaster.php:122)

Which means it throws on this piece of code:

I have a live app which was working fine and the work flow is

someone click on call from web -> voip push is sent to iOS device -> it shows callkit ringing ui-> user accept the call .

But now nor the live app neither the new release build getting voip push . and not incoming call is showing in phone.

i tried to send the voip push from Pusher but its is giving me error for "Unable to read: Read connection closed "

Voip push certificate is valid till October 21.

I have a live dashboard which displays data from a e-sports match. The data comes in trough pusher on the channel csgo and the event name is match-data-csgo.

Receiving the data when there is a new event is no problem, but I'm looking for a way to get the last event it's value. They pass a json in the event as value and from this json I can fill my page with content.

I'm working with Laravel and Laravel Echo and LiveWire. This is the code that works on a detect of a new event:

When trying to start Yagna I receive this error, what can I do? I can probably get some DEBUG logs if needed?

So I made a little chat functionality in laravel using pusher so it updates in real time. I have an event with the following methods I call using broadcast(new MessageSent($message, $conversationId)); whenever a message is sent.