Replies: 1 comment 1 reply
-
check this: https://stackoverflow.com/questions/78383337/solution-laravel-reverb-does-not-work-in-production-with-apache |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I did check out the other issues which were similar but they don't exactly quite fit my scenario.
I am on a shared hosting trying to run Laravel Reverb in production. Locally it works fine.
Here is my .env:
`REVERB_APP_ID=504618
REVERB_APP_KEY=nelnxsrzsy6ijdqzkixe
REVERB_APP_SECRET=nic8gwfsl7cydwhgcu2n
REVERB_HOST="pogotrades.com"
REVERB_PORT=443
REVERB_SCHEME=https
VITE_REVERB_APP_KEY="${REVERB_APP_KEY}"
VITE_REVERB_HOST="${REVERB_HOST}"
VITE_REVERB_PORT="${REVERB_PORT}"
VITE_REVERB_SCHEME="${REVERB_SCHEME}"`
My .htaccess:
You can see that I have commented out the 0.0.0.0 ip because I was testing both and both 127.0.01 and 0.0.0.0 result in same issue. Where I am stuck is that I ran this command using screen so that it never stops and it recieves a connection request, it says connection established but in front-end for client no response is received. After timeout the connection is closed by client and retried automatically and then I am stuck in a loop.
Below is laravel reverb:
Here is network request response after timeout:
Here is my Echo.js file:
Here is my reverb.php:
Any solution or idea what I am doing wrong or what's messing this stuff up?
Beta Was this translation helpful? Give feedback.
All reactions