I want to update my server with the latest version of parse server, but I am running into the issue where are all the calls send back a 403 Forbidden.
The exact same calls work on 2.2.23 and below but not on 2.2.24 and above. I am using parse for an iOS app, where I am using SDK 1.14.
Notes on the setup:
added VERBOSE environment variable, logs correctly on 2.2.23 but nothing on 2.2.24
running the server in localhost with node v6.9.1 installed.
pointing to a DB in mLab with mongod version: 3.0.12.
using express "~4.14.x"
Reviewed issues:
https://github.com/ParsePlatform/parse-server/issues/508 Where the
user was able to fix it by starting from scratch with
parse-server-example. I have tested this, using my ParseServer
instantiation and copying over the cloud code, I am having the same
issue.
https://github.com/ParsePlatform/parse-server/issues/1017 Was about
passing the X-Parse-Application-Id, which I am doing since it is
working for 2.2.23 but not for 2.2.24 and higher
Has anybody experienced something similar? Any hint on what I could try?
Thanks!
Related
I have a react-native application that was working fine until last week when I started getting this error. Now when I make an https request, I get this error 'Network request failed' on both IOS and android. Whereas when I request using http it works fine.
TypeError: Network request failed
at fetch.umd.js:535:18
at JSTimers.js:250:18
at _callTimer (JSTimers.js:146:7)
at Object.callTimers (JSTimers.js:399:7)
at MessageQueue.__callFunction (MessageQueue.js:436:42)
at MessageQueue.js:111:12
at MessageQueue.__guard (MessageQueue.js:384:9)
at MessageQueue.callFunctionReturnFlushedQueue (MessageQueue.js:110:10)
at debuggerWorker.js:69:58
For testing purpose I have tried to make an https request from same react-native application to the dummy apis available on internet it works fine. Moreover, I have also installed the previous stable version of the application that was working fine before but getting the same error on this as well. So, from that I'm assuming that issue might be from the server end but I've not made any noticeable changes to the server that could make it behave like that.
The strange thing is that the server is not showing any request in the logs coming from the react native application but it works fine when I request it using the postman application.
I've tried every solution that was available on internet but nothing worked. Moreover, I've tried using fetch and axios both to send request but the issue persists.
I have also checked the ssl certificates are installed, valid and trusted. For server I'm using the rails puma along with Nginx server.
Below are the details of the version of my application.
React Native
react-native-cli: 2.0.1
react-native: 0.61.5
Nginx
nginx version: nginx/1.14.0 (Ubuntu)
Rails
Rails 5.2.2.1
ruby 2.6.8p205
puma 3.7
Ror Experts,
I am having some kind of routing issue (I think so..). The Ahoy tracks visits and events in the development environment - running under webbrick server. When the application is deployed using warbler and published to apache tomcat server, it throws 500 error, Wrong number of Arguments (given 0, expected 1) while trying to log events. Tracking visits works as expected.
I have already tried suggestions mentioned in ahoy github account (https://github.com/ankane/ahoy/issues/356) without success.
I tried to debug if the data from react code is sending data as expected. It is indeed sending the data. I tried to post the data using postman directly to the controller using the same load to both development and deployed environment. It works on development but not on deployed.
I also tried to check error logs on the server. There is no information except 500 error.
Can someone help me out...
PS:
Prod server: Apache Tomcat
Environment: Jruby on rails
Front End: React
Found a solution. Fixed using gem as integral part of application instead of gem...... Still doesn't know what caused the issue. My gut feeling is some kind of routing issue with jruby and bundler warbler.
Is there any reason a postman post request would work but the very same restsharp code gateway times out? I can still get the token just fine through restsharp, but when I try one request, it times out.
For what it's worth, I just battled with this error myself making a request to the exact same endpoint.
I had Restsharp installed via the NuGet Package Manager and then installed the Elli.Api package. Once I installed this package the timeout errors started, but were not happening before (Note: I was making direct API calls and not using the EllieMae dotnet bindings, but installing the Elli.Api package still caused timeouts).
What seemed to work for me is installing the Elli.Api package, then uninstalling Restsharp and reinstalling it. Requests seemed to function normally after this.
One other note: the Restsharp package I used was 106.2.2 both when I uninstalled it and when I reinstalled it.
EDIT: Doing this seems to cause various errors when you try to use the dotnet bindings (such as a missing method error when trying to use GetAccessToken).
I've just started integrating towards my new OS X local server installation but I get an issue whenever I'm running an integration from Xcode on it. The tests seem to run but I get an error that the request times out. Also, the tests tab is completely empty. See image:
I'm running Xcode 6.4 and Server 4.1.
Wow. I figured it out. This is one of those issues that nobody can possibly have the same solution to but I will tell you anyway. My problem was that I had pointed localhost to my VM, i.e. another IP than 127.0.0.1. When I changed this back it worked great!
I tried to deploy a Play app to Cloudbees (only via push to git repo from which it is built by jenkins), it compiled and should work but I get a "502 Bad Gateway" error when loading the app. There is no error shown in the console only that it answers "502 Bad Gateway" when trying to access it. But that's what I see in the browser, too.
Cloudbees say that there is no other manipulation necessary, just cloning/pulling the ClickStart-Project, making it you application and pushing it back. The Play project works fine locally.
I am very grateful for any help. Please let me know if I need to provide any other information. Thanks a lot!
Edit: It works fine with Heroku only adding a Procfile. I don't get the problem with Cloudbees...
In this case the error is due to the database needing evolutions to be run before it can start:
[warn] play - Run with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true if you want to run them automatically (be careful)
Oops, cannot start the server.
#6eg39l651: Database 'default' needs evolution!
You can see the error in your application console:
https://run.cloudbees.com/a/strehlst#app-manage/logs:strehlst/odzh
or via bees app:tail if you have the bees CLI installed.
You can also deploy direct from your desktop if you like:
play dist
bees app:deploy -t play2 dist/yourapp.zip
And it will push direct to your app (if you don't want a continuous deployment pipeline).