You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My backend runs on node.js on GAE. Using ws over http.
I installed pushpin on a Compute Engine instance and configured it. I can connect via ws to the 7999 port, but i get 502 error. I think there is something to do with over_http configuration, sending the request to the google app engine (only accepts https).
You haven't described much about how your server side code is set up, but when you connect to ws://xx.xx.xx.xx:7999/ws-dual-devices?deviceUUID=22c33b4dd97e, the https URL you should expect to be proxied to is https://xx.xx.xx.xx:7999/ws-dual-devices?deviceUUID=22c33b4dd97e.
I suspect the problem is the host header being sent by the websocket client (potentially of the form "xx.xx.xx.xx"). By default, pushpin makes an identical request to the target. This is not only the path and query params, but also the headers, including the Host header. So potentially, this is not being understood by GAE which no doubt uses the host header subdomain to figure out which app to route to.
I might guess that an earlier log entry shows pushpin routing to a URL that Google App Engine isn't understanding. In this case, you should use the host target parameter to fix this.
My backend runs on node.js on GAE. Using ws over http.
I installed pushpin on a Compute Engine instance and configured it. I can connect via ws to the 7999 port, but i get 502 error. I think there is something to do with over_http configuration, sending the request to the google app engine (only accepts https).
routes:
wscat -c 'ws://xx.xx.xx.xx:7999/ws-dual-devices?deviceUUID=22c33b4dd97e'
im getting 404.
Any tips?
The text was updated successfully, but these errors were encountered: