$e.bash-tian
Deno application with just a Websocket connection gives 504 in Prod Deno Deploy
UPDATE - I am pretty sure the issue is somewhere in the Deno Deploy not being set properly, I could be not handling as I should the websocket connection, when I checked with the data provider, they log the error as Client Disconnected, I have a console.error for the onerror and a console.log for the onclose...despite that I don't see anything in the deno deploy logs...I will probably simply run the deno server locally and spend time working on the UI
86 replies
Deno application with just a Websocket connection gives 504 in Prod Deno Deploy
Hi @NDH! im sorry I haven't had time to check the suggestions you made. Answering your questions, I go to Deno Deploy overview and open the site. You mean ping to keep it alive? Possibly with a similar approach to what you suggested, with the SSE
86 replies
Deno application with just a Websocket connection gives 504 in Prod Deno Deploy
ok...good news and bad news...deno ws is now working fine! bad news...for some reason, data stops being inserted to the database, idk if that is deno or vercel having a time limit
86 replies
Deno application with just a Websocket connection gives 504 in Prod Deno Deploy
yep, but if it runs locally, it runs just fine. I did some reading and some people seem to send pings to keep to connection alive but in my case, its not that the ws goes silent and then it stops, as you can see in the video I sent earlier, the browser never fully loads, so I guess thats why the timeout
86 replies
