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'
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!
A simple HTTP GET request.
When I put the URL into the browser bar, the results come back. (a small JSON object)
When I put the same url into Postman (https://www.postman.com/) I got the following 403 error back:
ERROR: The request could not be satisfied
403 ERROR
The request could not be satisfied.
Bad request.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: xxxxxxxxxxxxxxxx
What is causing this and how can I use Postman on API Gateway in AWS?
As a further clue to the puzzle - when I change the request type of 'post' in postman, I get the expected response for an undefined resource: {"message":"Missing Authentication Token"}
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.
First, when trying to deploy my code to the target url in gcloud, the deployment process hangs.
The target url has the suffix appspot.com.
When I ping the target url, I get a request timeout. When I type the target url in my browser, I get a 502 error: server error.
When I deployed the same code to a different test environment in dialogflow, everything seemed to work fine. However when I try deploying again to this url (it is the correct url obtained from the webhook fulfilment url in dialogflow), I get this error:
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for
the app infrastructure to become healthy.
Everything else, including the node js code and the dialogflow configurations are the same between the two environments I am deploying to, except for the webhook fulfilment url.
Does anyone know what the issue can be narrowed down to? And please let me know if I can include any more useful information.
My guess is that the server is down for that specific URL. One thing to note is that I am using V1 dialogflow.
Resolved, it ended up being a firewall issue for that specific url.
[2017-10-31 18:38:43,008] [] ERROR - FilePollingConsumer Repeatedly
failed to resolve the file URI:
ftp://username":#"servername/folder/folder/folder/
org.apache.commons.vfs2.FileSystemException: Invalid absolute URI
"ftp://username":#"servername/folder/folder/folder/".
Caused by: org.apache.commons.vfs2.FileSystemException: Expecting / to
follow the hostname in URI
"ftp://username":***#"servername/folder/folder/folder/".
Tried several options, still not working. I used FTP url syntax/format from previous StackOverflow WSO2 postings and product documentation, but did not work. what am I doing stupid?
adding vfs.passive=true in the FTP URL did the magic. FTP inbound endpoint works fine.