Trying to use skype interviews api, but not working & hitting an error as 502 - webserver

While running curl to make http post request to skype interviews api, it is hitting an error as 502 - Web server received an invalid response while acting as a gateway or proxy server. There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the conerror in command linetent server.
I am running a command as "curl http://interviews.skype.com/api/interviews -H 'skype-apikey: my api key' -d {}".
By searching, many suggested to check that both IIS versions must be matched, and increase the ARR timeout to 60/120 secs in IIS. Both are not working for this.
Can anyone help me out in using the skype interviews api for performing internal communication like text/audio/video chat, sharing files/screen by any text or video tutorial. Help will be appreciated. Thanx in advance.

Step 1: I have implemented skype interviews API in NodeJs.
First Get your API key and secret:
Step 2: After that create API_KEY and API_SECRET environment variables in the .env file and assign values to them which we got from step 1.
Step 3: Follow the following link for source code to hit skype interviews API endpoint
https://gist.github.com/RajuS1ngh/8729fd8f047a20eed0fe1271c982d122

Related

VSTS connection with SOAPui via ReSTapi

I am trying to make connection to Azure VSTS with SOAPui through vsts rest api's, but the response I am getting is: HTTP/1.1 203 Non-Authoritative information
Though when I hit the same request from POSTMAN it's giving successful response for every operation(Get, Post, Delete).
As I have a framework for API automation in SOAPUI I need to have this connection to post the test results in VSTS against respective test case.
Any idea how to resolve this would be much appreciated!!
Thanks
This is due to the incorrect authentication headers (Authorization header) that you send in the request. I have experienced this issue when you are trying to send empty username in SoapUI - Basic Authorization tab.
This can be handled by generating the header offline (using some online utilities - https://www.blitter.se/utils/basic-authentication-header-generator/) and sending in a separate header like below,
Authorization: Basic Onl1eWl1eWl5aXlpeWl5aXk=
Hope this helps.

Facebook Product Feed Schedule using ShareFile FTP Link - curl error 56

I'm attempting to set up a scheduled fetch for a product feed in Facebook Business Manager. From what I can see, I can provide an FTP link to Facebook along with credentials and it should pick up the file.
The FTP provider I'm using is ShareFile, with the appropriate account given access to the folder the file is in. I confirmed I can use these credentials and connect to the FTP using FileZilla, so that portion should be solid. The setup in FileZilla is as follows:
Host: host.sharefileftp.com
Protocol: FTP
Encryption: Require implicit FTP over TLS (port 990)
User: domain\facebookfeed#host.com
Password: ######
However, when I put the same credentials into Facebook Business Manager for the feed upload, I get the following error:
Fetching product feed from FTP server failed due to unknown reason
(Curl error code: 56). Please help us by reporting the problem. You
may be able to try again.
All I can find on this error is from the cURL error page:
CURLE_RECV_ERROR (56)
Failure with receiving network data.
I saw a mention somewhere about needing to whitelist Facebook's IPs within ShareFile, but I can't for the life of me find that page.
FTP Details are set up in Facebook as follows:
URL: ftp://host.sharefileftp.com:990/Path/To/File.csv
Username: domain\facebookfeed#host.com
Password: ######
I've been unsuccessful getting anywhere else with the Facebook documentation and I can't find a way to contact their support directly. If anyone has experience with this any help is appreciated!
EDIT: Trying this just with a direct cURL and getting the same results:
$ curl -u 'domain\facebookfeed#host.com' "ftp://host.sharefileftp.com:990/Path/To/File.csv"
Enter host password for user 'domain\facebookfeed#host.com':
curl: (56) response reading failed
So at this point it's probably just an issue with ShareFile itself, nothing to do with Facebook.
As #jared pointed out in the comments, using ftps did allow the cURL to work:
$ curl -u 'domain\facebookfeed#host.com' "ftps://host.sharefileftp.com:990/Path/To/File.csv"
However, Facebook doesn't support ftps. It only supports ftp or sftp, which ShareFile doesn't support.
The normal ftp I originally tried didn't work because the ShareFile account used didn't have normal ftp allowed. Once that was turned on, Facebook was able to connect to ShareFile and grab the file successfully.

debug rest call in wso2 api manager

I am connecting rest api call with wso2 api manager. I followed the steps from wso2 site
I am able to connect with rest api on my computer but following same procedure on another computer returns "Error: No Response from Server"
I had also configured the files as described here
Does anybody knows how to debug what is going wrong there ?
You can enable wirelogs and headers in API Manager to analyze the request response flow.
Open log4j.properties file in /repository/conf directory.
Uncomment the following loggers.
log4j.logger.org.apache.synapse.transport.http.headers=DEBUG
log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
Save the changes and Restart the Server
Invoke the API.
Regarding your "Error: No Response from Server" response, other than the CORS issue, this can occur due to browser certificate issue as well.
Therefore, first check whether you can invoke the same API using a rest client like curl,
if yes
go to your browser, accept the certificate for the gateway URL and try out invoking the API again.

Facebook Real-time Updates: (#2200) callback verification failed, code 2200

I am trying to get realtime updates from facebook for my application as documented in https://developers.facebook.com/docs/reference/api/realtime/. I am struggling now when it comes back to the Subscription Verification. I have set up a callback server which accepts both GET and POST requests. I verified that the server works by making curl requests to it.
However, I stil get this error when attempting to create a subscription issuing the POSt request below
{"error":{"message":"(#2200) callback verification failed:
","type":"OAuthException","code":2200}
From what I read in the documentation and other threads, I assume that this means that the single GET request to my callback URL fails. The callback url does not get requested by neither GET nor POST requests indeed. I suppose that facebook is somehow blocked from accessing the endpoint. However, I am able to auth as a user using the auth dialog (https://developers.facebook.com/docs/reference/dialogs/oauth/) where I pass a callback url on the same server as well. The server runs http (for now).
This is the curl I am using to post the subscription. Host file has an entry to redirect dev.minggler.com to localhost =>( 127.0.0.1 dev.minggler.com)
curl -XPOST 'https://graph.facebook.com/256139341164822/subscriptions?callback_url=http%3A%2F%2Fdev.minggler.com%3A3000%2Ffacebook%2Frealtimeupdates&object=user&fields=friends&verify_token=abcd123&access_token=$MYTOKEN'
Can anybody help me out on this?
finally found the problem. the server wasn't reachable from outside. resolving it solved the problem

Facebook [function.file-get-contents]: failed to open

I am geting function.file-get-contents failed to open when i try to connect with server , my server fails to connect ,same application work in all server but in my server i am getting this error , Any solution , is that server CONFIG Issue ..
YOU CAN CHECK SERVER Config here http://gomandi.com/phpinfo.php
In the last few days I saw a few complaints about file_get_contents not working well when trying to access facebook api using it.
Take a look at these threads:
Getting 404 Error from Facebook Graph API
Facebook Auth with high traffic sites: empty access tokens, empty /me
Facebook API 400 Bad Request
You might find out what's wrong there. I suggest that you try to use something other than file_get_contents, such as curl, which was suggested in those threads as well (along side some code snippets)