I getting a timeout connecting error on server post integration. So this is the exception i getting on server post.
Your submission was saved, but an integration error occurred. Please contact the form owner. Timed out connecting to: (server post url).
The timeout error was happened while using third party's dll or package. so you can response success message quickly and do a process on background. I meant, use threading concept.
Related
I'm trying to trigger a jenkins job using the API. I got the set the token, got to run it successfully in the browser and got a json output from the API call using:
https://<MY_JENKINS_ADDRESS>/job/path/job_name/api/json/build?token=my_token
I tried to use this call in a POST or GET web activity in Azure Data Factory but I'm getting this error:
Error calling the endpoint '<MY_JENKINS_ADDRESS>'. Response status code: 'NA - Unknown'. More details: Exception message: 'NA - Unknown [ClientSideException] Invalid Url:https://<MY_JENKINS_ADDRESS>/job/path/job_name/api/json/build?token=my_token. Please verify Url or integration runtime is valid and retry. Localhost URLs are allowed only with SelfHosted Integration Runtime'.
Request didn't reach the server from the client. This could happen because of an underlying issue such as network connectivity, a DNS failure, a server certificate validation or a timeout.
It is clear data factory can't access the url. How can I solve this issue? Any thoughts?
I am assumimg that the <https://<MY_JENKINS_ADDRESS/job/path/job_name/api/json/build?token=my_token>> is not a publically available and if that the case you should know that with ADF you can only access public facing urls . What that means is that If there anything whch is running on my local network or say on my laptop , ADF will be not abe able to access that .
So, I've set up my publishing with the exact same data as my filezilla client, I made sure I wrote the same credentials and it stablishes connection with it since it asks for the login credentials, but once I put the login info and click on accept, publishing cancels and gives me an error: "Website cannot be created 'sftp://blablabla.com/folder'. The server connection timed out.
Any ideas what could it be?
I am linking this file for my media URL:
my goal is for this to be sent as a MMS. I first had a file size error. I fixed that, now I am stuck with this error.
The video will play on my browser. But not on my phone, but it will play on my laptop.
Does anyone have any ideas what I might be doing wrong?
HTTP retrieval failure: Attempt to retrieve media failed. Possible
Causes Web server returned a 4xx or 5xx HTTP response to Twilio
Misconfigured Web Server Network disruptions between Twilio and your
web server No Content-Type header attached to response Content-Type
doesn't match actual content, e.g. an MP3 file that is being served
with Content-Type: audio/x-wav, instead of Content-Type: audio/mpeg
Possible Solutions Double check that your TwiML URL does not return a
4xx or 5xx error Make certain that the URL does not perform a 302
redirect to an invalid URL Confirm the URL requested is not protected
by HTTP Auth Make sure your web server allows HTTP POST requests to
static resources (if the URL refers to .xml or .html files) Verify
your web server is up and responsive Check to see that the URL host is
not a private or local IP address Verify the ping times and packet
loss between your web server and www.twilio.com
Error Description There was a failure attempting to retrieve the
contents of this URL. An 11200 error is an indicator of a connection
failure between Twilio and your service. When Twilio requests a page
from your server, we wait a maximum of 15 seconds for a response. A
connection failure will occur if no response is returned in that time.
There are many reasons a connection timeout can occur; common causes
are long running database queries or outside processes and calls to
external systems taking a long time to return. It may be possible your
application experienced one of these issues. If you are encountering
this error only intermittently, it is possible that your web server
was temporarily unavailable or experiencing a network outage. 502 Bad
Gateway errors If your debugger is reporting a 502 Bad Gateway error,
this may mean that Twilio's internal server had trouble retrieving
content from your website. Your request must contain a Content-Type
that is valid. Twilio may also have had problems resolving your DNS
name to an IP address, or issues with the network connection. Check
that your web server is started, and is available over the public
Internet.
Request Inspector
+ Expand All
GET https://meetlete.com/media/small-met.mp4 2021-02-21 05:05:07 UTC404 Request URL Parameters Message TextShow Raw
Msg "Attempt to retrieve media failed."
httpResponse "404"
EmailNotification "false"
url "https://meetlete.com/media/small-met.mp4"
LogLevel "ERROR"
Twilio developer evangelist here.
It might be the case that Twilio cached a 404 response to your video at some point. I just tried sending a media message using your URL and it was processed correctly and the video was ingested by Twilio.
I would advise you try again. If you still find that your account has cached the URL response, you could try moving the video to a different address and trying with that instead.
I've been running into some issues with the twilio and bot framework channel integration.
In a nutshell, a large number of incoming messages and conversations that happen through the twilio channel time out and the user never receives a response. Then, after a few minutes, all the piled up responses will arrive at the same time - almost as iff the responder hangs and then continues. The error occurs only with the twilio channel - the bot it working perfectly when embedded in site, when tested in azure portal, and when connected to slack.
When I first connected twilio to the bot, it was running completely fine for a few days, and now I am getting the following error on roughly 70-80% of the messages which occur through that channel.
On a high level, the error I'm getting specific to the channel is: 'There was an error sending this message to your bot: HTTP status code GatewayTimeout'
Inside of the app logs, the error recording is far more detailed, but still provides no insight into what specifically is causing the error:
HTTP Error 500.1013 - Internal Server Error
The page cannot be displayed because an internal server error has occurred.
Most likely causes:
•IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
•IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
•IIS was not able to process configuration for the Web site or application.
•The authenticated user does not have permission to use this DLL.
•The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
Things you can try:
•Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
•Check the event logs to see if any additional information was logged.
•Verify the permissions for the DLL.
•Install the .NET Extensibility feature if the request is mapped to a managed handler.
•Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
On the twilio side, I get the following error
Error - 11200
HTTP retrieval failure
Possible Causes
Web server returned a 4xx or 5xx HTTP response to Twilio
Misconfigured Web Server
Network disruptions between Twilio and your web server
No Content-Type header attached to response
Content-Type doesn't match actual content, e.g. an MP3 file that is being served with Content-Type: audio/x-wav, instead of Content-Type: audio/mpeg
Possible Solutions
Double check that your TwiML URL does not return a 4xx or 5xx error
Make certain that the URL does not perform a 302 redirect to an invalid URL
Confirm the URL requested is not protected by HTTP Auth
Make sure your web server allows HTTP POST requests to static resources (if the URL refers to .xml or .html files)
Verify your web server is up and responsive
Check to see that the URL host is not a private or local IP address
Verify the ping times and packet loss between your web server and www.twilio.com
Twilio sends a request to Bot Framework, and gets the following info back
Msg "Bad Gateway"
sourceComponent "14100"
ErrorCode "11200"
EmailNotification "false"
httpResponse "502"
LogLevel "ERROR"
url "https://sms.botframework.com/api/sms"
Twilio was unable to fetch content from: http://sms.botframework.com/api/sms
Error: Total timeout is triggered. Configured tt is 15000ms and we attempted 1 time(s)
Account SID: redacted
SID: redacted
Request ID: redacted
Remote Host: sms.botframework.com
Request Method: POST
Request URI: http://sms.botframework.com/api/sms
URL Fragment: true
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Some additional information:
Bot is working perfectly when embedded in website, when tested in the azure portal, and when connected to slack.
Error seems to occur at the locations in code where await context.sendActivity(messageToReturnToUser) or await dialogContext.beginDialog(this.id) or basically anywhere where we send something back to the user.
After a few minutes, bot framework will send all the piled up messages to the end user and they'll get a chunk of sms messages back to back.
Error cannot be replicated in any other channel or in the bot framework emulator.
Error does not occur with every message. An arbitrary number of messages will go through fine and get responses immediately, but then an arbitrary number of messages will be subject to the delays.
I am using paid twilio numbers, no trial errors happening here!
Has anyone else had this problem? Any input or help would be appreciated!
This issue has been mitigated on the Azure/BotFramework side. If you are still having issues, please let me know.
I think we just discovered a bug on iOS 9 (version as of Oct 23rd 2015) when using client SSL certs to talk to a backend API. In common with a lot of REST services, our API generates 4xx error codes to communicate status. One of those is a 403 Forbidden error when a client tries to access paths that a specific client ID is not authorized to access. Note that this HTTP error occurs AFTER the client SSL cert has setup a valid connection & and the client ID has been authenticated.
In iOS 9, this sequence will generate an invalid client SSL error:
FAILED: Error Domain=NSURLErrorDomain Code=-1206 "The server “our.server.here” requires a client certificate."
(note: this a followup to my tweet here: https://twitter.com/ckmaresca/status/657576686318256128 - I figured SO is the place most people will search for this)
It took us days to finally figure out but it turns out that this particular error is generated by Apple's new Application Transport Layer security. Specifically, it seems that if you are using client certs and your backend API generates an HTTP 403 error, ATL believes that the cert is bad and kills the entire transaction.
We know this because we can see in our server logs that the request goes through and executes properly. We've also observed that the socket stays alive trough the request and this error only shows up after the response from the server is received. We also know our client cert works since any path not returning a 403 works with zero errors and changing the HTTP error code to 401 makes this problem go away.
This is problematic for a number of reasons, but mostly because HTTP errors are not SSL errors. The two can operate independently and it's perfectly possible to have a 403 error with a valid client side SSL certificate....
The work around is to change all your 403 errors to something else. I would note that a large number of Oauth1/2 servers will generate various 403 errors, so this might be non-trivial. Alternatively, it might be possible to use a reverse proxy to remap HTTP 403 errors to a different HTTP code - we have not tested this.
We have filed a bug with Apple, but I wanted to give people a heads up so maybe they can avoid banging their heads against a wall like we did for a week....
Thanks to the Sherbit.io enginnering team (specifically Varun & Matt) for debugging this.