We have an application using AWS SDK AmazonS3Client to communicate with the S3 service to get files downloaded. With thousands of instances running fine, however, we got a few sites getting the following exception error message:
The remote certificate is invalid according to the validation procedure.
The versions of the AmazonSDK.S3.dll and AmazonS3.Core.dll we're using are 3.3.102.18 and 3.3.103.1 respectively. These had been running for over a year without problems until recently.
Has anyone else experienced the similar issue? What could be the root cause of the problem? How do we resolve it?
Thanks!
This has been determined as an issue with proxy server loaded with incorrect certificate from the service provider. So, not really the application issue.
Related
We are trying to reach to an API hosted in our company network using rest connector in ADF (SHIR is used). Linked service connection is successful but dataset is unable to read the data and copy activity is as well failing with below error. Please suggest your thoughts in resolving the same.
Failure happened on 'Source' side. ErrorCode=UserErrorFailToReadFromRestResource,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=An error occurred while sending the request.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=System.Net.Http.HttpRequestException,Message=An error occurred while sending the request.,Source=mscorlib,''Type=System.Net.WebException,Message=Unable to connect to the remote server,Source=System,''Type=System.Net.Sockets.SocketException,Message=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 ,Source=System,'
This error is mostly seen due to firewall issues. You might want to verify your network firewall setting to allow the API request to be read.
Also, verify if your API call is working as expected using other API testing tools. If the issue persists you can raise a support ticket for engineers to investigate more on the issue.
If you are able to preview data in your source , then check your sink connection as this issue can occur when the Sink in the copy activity is behind a firewall, I was getting the same issue and I tried copying to a container without a firewall and it worked. Its weird that the error is related to Source and the issue is with Sink.
We have been running a service using NestJS and TypeORM on fully managed CloudRun without issues for several months. Yesterday PM we started getting Improper path /cloudsql/{SQL_CONNECTION_NAME} to connect to Postgres Cloud SQL instance "{SQL_CONNECTION_NAME}" errors in our logs.
We didn't make any server/SQL changes around this timestamp. Currently there is no impact to the service so we are not sure if this is a serious issue.
This error is not from our code, and our third party modules shouldn't know if we use Cloud SQL, so I have no idea where this errors come from.
My assumption is Cloud SQL Proxy or any SQL client used in Cloud Run is making this error. We use --add-cloudsql-instances flag when deploying with "gcloud run deploy" CLI command.
Link to the issue here
This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Your application is working correctly and should not receive this warning.
Thank you for reporting this issue. The fix is ready and should roll out soon. You should not see this message anymore after the fix is out.
I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!
I have an SSIS package that calls an SSRS report hosted on a local server that produces a series of PDFs. It has been working perfectly for months, but all of the sudden I am now getting this error:
Error: 0xC001600B at SSIS_Package, Connection manager "ReportServer": The specified server, URL http://server/report¶meter1=401¶meter2=13&rs:Command=Render&rs:Format=PDF, has a redirect and the redirect request failed.
I have checked all my credentials in the package and on the server and everything is connected properly. I haven't been able to find anything at all about this error and I'm hoping someone out there has come across it!
It turned out to be a permissions error that was resolved by another user running the package.
After I have added a service dashDB to my Bluemix application and I click on it, I got in IE11 this message:
The website declined to show this webpage
HTTP 403
When I did the same in the Google crome I got a square head which looked sad.
Does anyone know what to do?
Thank you!
There is not much information to go but I would suggest the following to narrow down the cause of the problem or resolve the issue:
- verify that service has been provisioned successfully (unless it's an existing instance that is known to work in the past)
- clear browser cache/restart to eliminate any transient issues
- BlueMix status page (https://developer.ibm.com/bluemix/support/#status) is currently reporting some authentication issues which potentially could cause problem, it should be check if the 403 error is still reported after the problem is resolved.
It might be worth to create the service with the "leave unbound" option and try to click on it. After you could bind it to your app.
You can verify if the dashDB instance is up or not by accessing the https_url from the VCAP variable associated with the dashDB instance (for e.g.: https://bluemix05.bluforcloud.com:8443) and provide your username and password (also from the VCAP variable) for that instance and see if you can log in.