Issues with Pusher in production | Laravel | Page 1

graceful pendant Oct 10, 2022, 6:47 PM

#

Do you have any errors in your browsers JS console? Could be many things, like not using https pusher connection when your site itself is serving via https, etc.

spice pollen Oct 10, 2022, 6:48 PM

#

graceful pendant Do you have any errors in your browsers JS console? Could be many things, like n...

I've had those before, but currently it comes up with no console errors. First issue had to do with the unavailability of env variables in the pipeline.

graceful pendant Oct 10, 2022, 6:49 PM

#

Do you even see a websocket/http fallback connection to pusher at all in your network request?

spice pollen Oct 10, 2022, 6:50 PM

#

let me take a look, might be broken at this point honestly.

#

at the beginning before starting to troubleshoot I got 500 errors every x seconds

#

let me roll some changes back and see if I can get back to that.

graceful pendant Oct 10, 2022, 6:51 PM

#

Mkay

spice pollen Oct 10, 2022, 6:57 PM

#

yup there we go, connection failed

#

have a feeling it might have to do something with the way I set it up in broadcasting config file

graceful pendant Oct 10, 2022, 6:59 PM

#

in your JS you mean, or the backend?

#

Think you mentioned the backend was properly hitting pushers API

spice pollen Oct 10, 2022, 7:00 PM

#

it is, for actually broadcasting messages

#

but it's not able to subscribe itself

#

let me see if I can share some stuff that perhaps clears it up a little

graceful pendant Oct 10, 2022, 7:00 PM

#

I have not used pusher directly for a good while, but at least ensure you are using the right production keys in your JS build, as well as the cluster etc

spice pollen Oct 10, 2022, 7:02 PM

#

but the normal process of setting up a connection and listening on said channel does not

graceful pendant Oct 10, 2022, 7:02 PM

#

On your client side you mean?

#

Check XHR/WS tabs in your network request, see if anything is reaching out to pusher, and if so, what its errors are

spice pollen Oct 10, 2022, 7:04 PM

#

yup

#

let me compare this to what I call out locally

#

right this is pretty strange..

#

seems like in production it calls out to a ID instead of an encrypted version of it.

#

or hashed.. not sure what the process exactly is internally

graceful pendant Oct 10, 2022, 7:07 PM

#

If you click on the failed request, does it tell you why?

#

Not sure what you mean encrypter/hashed. The endpoint it hits in your browser will always be the public keys/IDs

#

only your backend that directly hits the pusher API uses the secret keys

spice pollen Oct 10, 2022, 7:08 PM

#

they didn't fail, they're stuck on pending

#

but for example if the url is

#

wss://28ahe13kjd?protocol=7 etc etc

#

works

#

but in production it's like:
wss://3571835?protocol=7 etc etc

graceful pendant Oct 10, 2022, 7:10 PM

#

Well your app ID will definitely be different between your dev/sandbox vs production

spice pollen Oct 10, 2022, 7:10 PM

#

yes

#

but it seems like locally

#

it changes my pusher key to something else

#

while on production it takes the literal key

#

oh my.. I think I see something, one moment

graceful pendant Oct 10, 2022, 7:11 PM

#

Mkay, because so far not sure I have much else to go on 😦

spice pollen Oct 10, 2022, 7:11 PM

#

locally it picks the wsHost, in production it takes the key itself

#

not sure why

graceful pendant Oct 10, 2022, 7:11 PM

#

Might want to define wssHost

spice pollen Oct 10, 2022, 7:11 PM

#

good call, let me give that a shot

graceful pendant Oct 10, 2022, 7:12 PM

#

lemme open up my chat app that used pusher, might see something

spice pollen Oct 10, 2022, 7:12 PM

#

appreciate it a lot

graceful pendant Oct 10, 2022, 7:13 PM

#

Seems if I use real pusher, I do not even define wsHost etc. Though my app is a demo and not been fully updated in some time

spice pollen Oct 10, 2022, 7:13 PM

#

let me check, the app I'm building is still in "testing" so no harm done

graceful pendant Oct 10, 2022, 7:13 PM

#

#

my second object is when using a drop in replacement like laravel websockets package

#

but top one being real pusher, I never defined the wsHost etc

#

hmm

spice pollen Oct 10, 2022, 7:15 PM

#

still seems to resort in a timeout

#

though this is drastically different from the implementation I have currently.

#

but you did run this demo on a production environment right?

graceful pendant Oct 10, 2022, 7:16 PM

#

even the docs show only defining the limited keys

graceful pendant Oct 10, 2022, 7:17 PM

#

spice pollen but you did run this demo on a production environment right?

Pusher is just an option to use, and my default for my public demo repo, however on my live demo, I do instead host my own using laravel-websockets

#

But I know locally it works as well

spice pollen Oct 10, 2022, 7:18 PM

#

I see, fair fair

#

that's the issue I have haha, locally it works like a charm

#

but let me reduce this to the docs recommended structure

graceful pendant Oct 10, 2022, 7:18 PM

#

Truth be told, just been a while since I truly interacted with the real pusher, been using drop-in replacements for some time now.

spice pollen Oct 10, 2022, 7:20 PM

#

might be overlooking it currently

#

but do you happen to see laravel's recommended setup for the config as well?

#

since this is client side, but broadcasting happens server side I think.

graceful pendant Oct 10, 2022, 7:20 PM

#

Might want to also clear your local app storage. AT least when using a drop in, if connection fails, pusher-js resorts to long polling and their local storage state messes me up

#

graceful pendant Oct 10, 2022, 7:21 PM

#

spice pollen but do you happen to see laravel's recommended setup for the config as well?

Yea, they do not define wsHost etc

spice pollen Oct 10, 2022, 7:22 PM

#

in broadcasting.php ?

graceful pendant Oct 10, 2022, 7:22 PM

#

https://github.com/RTippin/messenger-demo demo in question.

spice pollen Oct 10, 2022, 7:22 PM

#

let me take a look

graceful pendant Oct 10, 2022, 7:23 PM

#

Well if your backend is hitting pusher and showing up in their dash, then your backend config should be proper

#

seems fully a client side issue to me

spice pollen Oct 10, 2022, 7:23 PM

#

yeah, I have to agree

graceful pendant Oct 10, 2022, 7:26 PM

#

My actual JS is another repo, https://github.com/RTippin/messenger-ui/blob/master/resources/js/managers/NotifyManager.js#L129-L172 so you can see that code in question

#

Old, shit JS, but it "works"

spice pollen Oct 10, 2022, 7:28 PM

#

alright, let me have a read through that as well

#

but I'm just quite surprised

#

console shows pretty much the exact same call to pusher

#

as locally now

graceful pendant Oct 10, 2022, 7:29 PM

#

Yea, sorry I can't be of much more help. The only issue I've seen others have recently was an issue with pusher php-server backend version 7.2 not working with laravel-websockets etc.

spice pollen Oct 10, 2022, 7:29 PM

#

oeh getting a response here now

graceful pendant Oct 10, 2022, 7:29 PM

#

But if you are using real pusher, do not think that would impact you

spice pollen Oct 10, 2022, 7:29 PM

#

not in this cluster error now

graceful pendant Oct 10, 2022, 7:30 PM

#

An error is something at least lol

spice pollen Oct 10, 2022, 7:30 PM

#

yeah

#

better than just a plain 500

#

this is an actual response from pusher

#

we're getting there!

#

it uh.. seems to work

#

at least, I'm getting traffic now

#Issues with Pusher in production