We have exposed a url to Twilio to send the sms delivery status and it was working fine when we hosted our service in our own data center.
But we moved our services to aws ; Twilio is unable to call our service and it showing the below error
https://www.twilio.com/docs/api/errors/11200
please help
make sure your Elastic IP Address is reachable using TCP/443 (you enabled this on your EC2 instance, correct) and your application supports both GET and POST methods. Check the Debugger (small bug icon in upper right corner of console) for any relevant error messages, otherwise the error 11200 URL you provided has a lot of extra steps to check.
You should be able to reach your application via your web browser, for testing.
Which IP addresses will Twilio's requests come from?
Related
I have AWS API Destination, which is triggered by rule. I attached DLQ to rule and I am getting rejected messages, but I don't see any reason why this is happening.
Is there any way to get logs in Cloud Watch about errors in API Destinations/Connections?
There is no facility to see/log the API Destination responses in EventBridge.
I've been searching for exactly the same and come up empty.
The workaround for now is to instead target a lambda that does the API call instead.
I had been developed a telegram bot using Telegram.Bot.
I tried to rework with the bot, First I created bot using BotFather and got token.
I set webhook server api address in telegram api. But when I check webhookinfo it returns this error
https://api.telegram.org/botToken/getWebhookinfo
respone:
"last_error_date":1585419712,"last_error_message":"Connection timed out"
I checked it need TLS12 to have secure connection using
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
But It's not getting updates in my server and show time out error.
I tried posting using postman and ngrok to run on my iisexpress and I'm getting data and can sending messages to bot in my localhost.
But In hosting it's not working, whats wrong with new Telegram.Bot library or telegram server?
update
I checked with postman my hosting url, post man also cant connect to that url. what can be wrong with my codes?
This is response when i'm call update receiving URL in my hosting:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.34.35:443
I got problem, the certificate which we use should be valid one, not free.
For more information please study this link:
https://core.telegram.org/bots/webhooks
I'm developing a VoIP IOS app using SIP protocol. I have my own SIP parser library and I use GCDAsyncUDPSocket to send data to the server.
The problem is that I can't reach the server on double NAT with my app. I do PING and the server responds immediately PONG, but when I send a SIP package, I can't even reach the server.
I try to reach the server with other clients like Zoiper or Media5 and works perfectly. So I think i'm doing something wrong.
Make sure to:
include your private IP:port in the contact and via headers (not a wrong public address)
add the rport attribute to Via
make sure that the REGISTER message is well formed (is a valid SIP message)
If still doesn't work, check the server logs. If still doesn't work or you don't have access to the server logs, let me see your REGISTER message.
I have OpenVBX and just bought a new Twilio number. OpenVBX has been installed with the sid and token of the Active Twilio account. I can send text messages but not receive them. And I can't make any calls or receive them. I tried adding the number to a flow under Admin >> Number >> Numbers used on other Domains: hide. But get an error message.
VoiceFallbackUrl is not valid: http://localhost/openVBX/twilio-OpenVBX-5c97301-V2/fallback/voice.php
Spec:
Wamp Server on local computer.
PHP Version 5.5.29
cURL support enabled
cURL Information 7.42.1
Ricky from Twilio here.
In order for Twilio to access your website it needs to be available on a publicly accessible URL. We're pretty big fans of ngrok as a means of tunneling our localhost to a publicly accessible URL for this purpose. If you spin up ngrok and access OpenVBX through that ngrok URL it should resolve the "VoiceFallbackUrl is not valid" error you're receiving.
Let me know if that helps!
I'm currently receiving
{"code": 400, "error_type": "OAuthException", "error_message": "No matching code found."}
while attempting to get a user's access token on one of our servers. This is occurring while using the REST Client Chrome extension and from our web application, on one particular server.
I am able to receive the user's access token from my local machine and a different server using the same code and extension.
Could our IP have been blacklisted from receiving access tokens? Has anyone else run into this issue?
Thanks,
EDIT
Heard back from Instagram support, this was an issue on their end and has been fixed. Thanks for the help.
Yes your intuition is correct. It is likely that you made too many incorrect API calls that Instagram disabled your IP. I started dealing with Instagram API this week, at the beginning it was working but today I started getting the same error you got. The code also works fine locally or on any other machine. The only explanation to this is that my IP is blocked. Just switch your IP and you should be fine!
SOLVED:
The reason for this error is the ip address from which you are trying to connect to Instagram and get access_token. After contacting my network provider and changing my ip everything got fixed.
To figure out if your issue is caused by your local ip (not the server ip) try to connect to your app via mobile network or any other network different from yours:
- If it works you need to change your local ip.
-If it does not work - change your server ip cause it is probably banned by instagram for lots of malicious requests.
I was having the same trouble: users couldn't authenticate through Instagram and the error returned was "OAuthException" and "No matching code found." Started on 4/28/15 but didn't catch until two days later. Only in production, not staging, so it was almost certainly IP.
I posted to the Instagram developer help center (https://help.instagram.com/contact/438525166257277) yesterday at 7pm and the problem was fixed by this morning, with a cryptic email from their support at 11am ("The issue has been resolved").