hasura on render.com?

[cellog]

Hello. I've successfully built a node app on render.com that can access a hasura endpoint on the server-side. When I try to use a subscription from the client side with graphql-ws, it instantly disconnects. I can see in the logs that it is connecting and instantly disconnecting:

Feb 19 11:19:29 PM  {"type":"websocket-log","timestamp":"2022-02-20T04:19:29.201+0000","level":"info","detail":{"event":{"type":"accepted"},"connection_info":{"websocket_id":"<redacted>","token_expiry":null,"msg":null},"user_vars":null}}
Feb 19 11:19:29 PM  {"type":"websocket-log","timestamp":"2022-02-20T04:19:29.201+0000","level":"info","detail":{"event":{"type":"closed"},"connection_info":{"websocket_id":"<redacted>","token_expiry":null,"msg":null},"user_vars":null}}

In addition, in the browser, what I'm seeing is that it is receiving a native onerror event when the websocket attempts to connect, so the error is directly in the browser on connection, it will not succeed in connecting. I had misconfigured CORS in the past and saw a CORS-specific error. As you can see in the logs above, I fixed that - it is connecting on the server, just failing in the browser.

The same application works perfectly when connecting to the local hasura database on localhost.

I'm completely out of options and ideas here, any suggestions to debug this?

I've set up a local proxy so I can use ssl locally to debug this, connecting to the remote hasura server from my dev environment.

[cellog]

I figured out the issue: hasura does not support graphql-ws for wss (it's listed as beta, but probably should be listed as "does not work at all").

I swapped out for apollo transport and it worked right away.