No errors, no results about parselivequery-ios-osx HOT 8 CLOSED

Are you using a proxy in front of your Parse server, such as Nginx?

from parselivequery-ios-osx.

@Kenishi Yes, we are having similar issue, using Nginx and SSL with a reverse proxy with non root location. Any suggestion on the issue?

from parselivequery-ios-osx.

Be sure to you have Nginx setup to Upgrade the connection or the Web Socket protocol will never be able to fully connect.

See here: https://www.nginx.com/blog/websocket-nginx/

from parselivequery-ios-osx.

@Kenishi Thanks for the pointer, we have the following nginx config and it is still not working.

location /app/ {
      proxy_pass http://NodeServers;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection 'upgrade';
      proxy_read_timeout 86400;
    }

from parselivequery-ios-osx.

Hmm. The Nginx settings fixed all the problems I had. If you are connecting to Parse through mobile SDKs, then it might be worth it to try doing it through the JS SDK and see what errors it puts out since the iOS SDK wasn't very verbose on that sort of thing. Also, there is a way to turn on debugging for LiveQuery on the server which can show if its getting connections or not. Are your Nginx logs showing that its working fine? Its been a bit over a month since I had this problem but I seem to recall that Nginx was showing it was routing fine with a code 200 but nothing after that. Also I'm assuming if you try to visit the /parse api endpoint via browser you should be getting a {error:unauthorized} correct?

from parselivequery-ios-osx.

Thanks for the tips on troubleshooting. Yes to the {error:unauthorized} via browser but our end point is /app. Here is what part of the output when turn on the verbose log, status 201 for adding the message which is good. However, the last line location value seems to be wrong (without the endpoint and without the https) and could be the reason why live query is not triggered. our location value in nginx is /app/

Result in the parse-server console.

verbose: {
"status": 201,
"response": {
"objectId": "1Iusu3wtWC",
"createdAt": "2016-05-10T23:28:42.830Z"
},
"location": "http://api.myserver.com/classes/Message/1Iusu3wtWC"
}

from parselivequery-ios-osx.

Actually it looks like you found your problem in #33 . 👍 Its the /LQ issue.

(The pod will still have the old /LQ path, so you'll probably have to pull from the master)

from parselivequery-ios-osx.

@Kenishi The /LQ did resolved one of our earlier issue with establishing the ws connection/handshake. The problem we are still having is that now that the ws connection seem to be established, the LiveQuery are still not being triggered/not being routed correct. We feel the issue might still be at the reverse proxy side. Do you have an example of the nginx config that you can share? BTW, we are using SSL.

We also tried the echo test for the ws.
http://www.websocket.org/echo.html

The connection works, but as soon as sending a message, it automatic disconnects. Any thoughts on this?

from parselivequery-ios-osx.