I am getting the error 'Error communicating with Amazon SNS API: There was a problem executing this request'
Anyone who has used Sendy and experienced the same error?
I had the same error and after looking into it there was a certificate issue. CURL was returning the error "SSL certificate problem: unable to get local issuer certificate" but this wasn't being returned within the UI.
I then followed these instructions for getting it working: curl: (60) SSL certificate problem: unable to get local issuer certificate
To see if you have the same error as me you can modify the sendy code slightly to output this error: within /includes/helpers/sns.php, line 463 output the curl error i.e. add the third line below:
$output = curl_exec($ch);
$info = curl_getinfo($ch);
print curl_error($ch);
reload the page, it won't be pretty, but if it's the same error as me you'll be able to fix it.
Related
I am having a recurring issue with shinyproxy (currently 2.5.0 - based on Springboot) hosted within a kubernetes cluster (currenty a single node). I'm using Auth0 with SAML. Traffic goes through a Nginx ingress controller that does TLS termination and has a fairly basic configuration. What I don't understand is that I will get the following error, but only once in a while. If I try to login, I will get the error, but then after that, if I go back to the login page and try to log in again, everything works fine.
o.s.security.saml.log.SAMLDefaultLogger : AuthNResponse;FAILURE;[Auth0 URN];;;org.opensaml.common.SAMLException: InResponseToField of the Response doesn't correspond to sent message a12g399012cidi7i2i3ha3ha4h6e6jc
at org.springframework.security.saml.websso.WebSSOProfileConsumerImpl.processAuthenticationResponse(WebSSOProfileConsumerImpl.java:175)
at org.springframework.security.saml.SAMLAuthenticationProvider.authenticate(SAMLAuthenticationProvider.java:88)
at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199)
at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:219)
...
This made me think of a cookies problem, however adjusting the shinyproxy server/proxy configuration for cookies did not change anything. Shinyproxy configuration has:
server:
secure-cookies: true
proxy:
same-site-cookie: None
In the browser when I try to log in I get the following error message:
Error
Status code: 200
Message: Error validating SAML message
Stack Trace:
org.springframework.security.authentication.AuthenticationServiceException: Error validating SAML message
...
Anyone has an idea of what I am missing? I would really appreciate it! Thank you!
I deployed the lex bot using https://aws.amazon.com/blogs/machine-learning/deploy-a-web-ui-for-your-chatbot/ this method.
I am getting the message:
"Sorry, I was unable to process your message. Try again later."
when I type some text, and in console when I checked I got status code 404 and response:
{"message":" ... is not a valid BotId/BotAliasId combination."}.
My lex bot and lambda function was in Singapore region and i was deploying it in Ireland. I deployed it in singapore and error was gone. But, new error was not able to see the image response card sent from the lambda function :(
I am getting an error while uploading an image to Facebook.
Both image and image path are proper but somehow it is not uploaded to Facebook when I am making a POST request to {pageid}/photos API call.
Here is my code.
$photoURL = 'https://www.example.com/images/img.png';
$uploadPhoto = $fb->post('/'.$pageId.'/photos', ['published' => 'false', 'url' => $photoURL]);
And it is giving following error.
Message: (#324) Missing or invalid image file
Please help me.
Thanks.
If you are trying to post from your localhost or virtualhost then error occurs because facebook can not find the url that you are providing.
Try this way:
search image from internet and pass its address to facebook SDK. I will post successfullty.
I was trying to send image from my virtualhost http:app.local.com/image-address and it gave same error. Then I picked an image form internet and passed then it was posted successfully.
Hope it solves your issue
For me it was the SSl certificate. It was on the server and valid over https, however I had an incorrect intermediate certificate on there. I saw the error when I checked the domain
https://cryptoreport.geotrust.com/checker/views/certCheck.jsp
Thanks
Grant
I have amazon command line tool to post HITs to Mturk. But there seems to be a problem with the mturk URL in mturk.properties. It keeps asking for https.
I searched for the solution in aws forums, with most stating simply change the URL from http to https. I have tried and get the following error
An error occurred while fetching your balance: >javax.net.ssl.SSLPeerUnverifiedException: HTTPS hostname invalid: expected >'176.32.98.23', received 'mechanicalturk.amazonaws.com'
I'm getting the following error when trying to connect to my testlink server after a test run:
br.eti.kinoshita.testlinkjavaapi.util.TestLinkAPIException: Error verifying developer key: Failed to read server's response: http
here is the string i use to create the testlink connection :
http://usrname:test#http://{ip_server}/testlink/lib/api/xmlrpc/v1/xmlrpc.php
Anyone could know what I'm doing wrong
The URL is invalid format!
http://usrname:test#{ip_server}/testlink/lib/api/xmlrpc/v1/xmlrpc.php
The extra "http://" in the middle does not belong!