My code runing test url is perfect working but when i run code in server https://secure.payu.in/_payment and key and slat key is not working
Please help me anyone
I was also facing the same problem but I have figured it out. It's just your merchant ID has not been verified yet so it will be redirecting to the test server even though you have passed https://secure.payu.in/_payment in the payu_base_url. Thanks
Related
I created my very first NODEJS API. Locally, it works well but I just hosted it on planetHoster and it doesn’t work anymore. When I enter my query, I find the error "Cannot GET/Nodev2/idcc/list" then my route was functional locally. Do you have any assumptions? Thank you in advance!
I can share my code if you want see
I tried to change directory/file names
I am trying to post a simple json to our backend api through REST POST snap. Everything was working. And then we changed the url to a new url and I updated the url in the snap.
But now request is simply not reaching our new api server.
In fact, the snaplogic pipeline also completes successfully, with all snaps turning green. Only when I click on the properties of pipeline, I get to know that REST POST snap has failed, with attached screenshot error.
Please note that we are able to reach the new api server via postman or any other rest client. Nothing has changed at all except for the url.
Can you please help me understand, what exactly is going wrong and where? How to debug this?
Just for everyone's reference, I was able to find out the root cause.
Reason was that the api url was not accessible to snaplogic pod running in our enterprise because of Zscaler firewall.
The confusing part here was the error message returned which says "SSL issue, connection was reset". So if you see issue saying "Connection was reset", assume that snaplogic is unable to access the url as the first problem. Only after making sure, it is not the case, go and look for what exactly the error says.
I encountered this problem today. It was working since last year, then started to throw error like
[400] Error connecting to the API
(https://na2.docusign.net/restapi/v2/accounts/f0332a4a-528a-4f7f-a506-f1a9be016ca1/envelopes)"
When I test the integration in dev mode. It works just fine. I think the api endpoint has a problem. This endpoint https://demo.docusign.net/restapi for demo works flawlessly.
The base URL could also be the problem. Is anybody from DocuSign team able to verify this? I can't seem to find the reason why. I tried to regenerate token and use it but no joy. Again it works fine in demo but not on any production baseUrl.
The code is written in PHP and I'm using the PHP sdk version of the docusign.
I have server based backend deployed on app engine and it's working(free trial), but it have too much resources. I want to deploy an updated version of it with more fine tuned app.yaml and some minor updates. The problem is: new version is not working. It have some redirect code and it works, when i directly type:
https://myapp/parse
it shows:
{"error":"unauthorized"}
it's all good.
But when i try to do login, or other CRUD it just writing logs and doesn't do anything.
Because of that all i can do is return traffic to old version, which is working just fine, and beg for help.
May be google did some updates in last month and i have to redo something in my app?
UPD
Backend always returns 307 redirect when i do authorized request, old(deployed in november 16) version works great.
It is not 100% clear for me the issue. If it is possible to show us the whole output.
But apparently, it is the HTTPS in your URL. Try it with HTTP. It is the most common scenario for the unauthorized error.
I'm trying to use the web api to query a user's playlists (using the spotipy Python library). I got the user to oAuth in, got an access token, made the request and got a 500 error:
SpotifyException: http status: 500, code:-1 - https://api.spotify.com/v1/users/125139403/playlists?limit=50&offset=0: Server error.
I then tried the same request in Web API test console and it worked fine.
But then things get kind of weird. I tried running the cURL command the console generated in a terminal and got the same 500 error.
Then I tried running the same request using cURL but just changing the username in the URL and it worked fine (at least for public playlists) for both my username and a random friend's user ID number.
I thought maybe I'm having a token issue but the token I'm using seems to work fine with other usernames. It's just the one specific user for whom I'm getting the error.
I'd rather not post the user's ID on this public forum but I can email it to someone if it's relevant.
My best guess for what's wrong at this point is a bug on Spotify's side but I certainly could be doing something wrong.
Again, thanks for reporting this. This bug was fixed by Matt M. and was just deployed to production.
Please try it out in our API Console. (which Matt was also part of building!)