Laravel-websockets: Cloudflare, Forge's Load balancer and SSL

Created on 15 Jan 2019  路  4Comments  路  Source: beyondcode/laravel-websockets

Has anyone managed to run the websockets server behind Cloudflare (with the orange arrow, not just redirect) which is pointed to a Forge Load balancer (SSL enabled) forwarding the requests to the 6001 port of the server where Websockets is running?

I'm not sure if I need the certificates inside the websockets config as well given that the traffic between the LB and the websockets server is not on SSL 馃

Most helpful comment

All 4 comments

Cloudflare only allows port 8443 for sockets. Try that port instead, and make sure it is open in Forge.

Gold! Thank you both. I will close the issue and post and update if further changes were required to get it to work. 馃檹

I don't suppose you managed to get this working? I can get everything working locally but receiving 404 when using Cloudflare > Forge load balancer > app server. I have Cloudflare set to redirecting only, usual options enabled such as allow Websockets.

I used to have Laravel Echo Server running which worked fine through Cloudflare and the load balancer but I cannot get Larevel-websockets working.

Was this page helpful?
0 / 5 - 0 ratings