Not sure if this is a Docusign or ngix question.I'm working on integrating an application with Docusign and I keep seeing this somewhat vague error below in the Docusign Connect logs. In our nginx logs I see that a POST to our application's /webhook endpoint was attempted but doesn't go through. I've specified TLS 1.2 and have tried increasing our nginx timeout but that doesn't seem to fix it.
One theory I have is that our server's certificate isn't chained to a Microsoft trusted CA but I would expect a different error if that was the case.
Any help or guidance would be greatly appreciated.
This most likely would require you to get the IT folks managing this server and networking involved. And yes, they may need to install a certificate, but other errors can be related to the firewall blocking certain requests, an anti-virus blocking requests and even DNS related error preventing the HTTP request from being sent and received by the server.
We highly recommend to use a public cloud for Connect and we have plenty of examples how this can work, while still having your code run on your own IT server.
Related
Our company CRM web application does not have an API and therefore is extremely cumbersome to use when having to upload data as this all has to be done manually and through the GUI. To access this application you need to be identified in GlobalProtect. My idea was to use http requests sent directly to the server to try to circumvent the lack of an API.
However, i have been very unsuccesful as copying http request out of the chrome devtools and changing their payloads using Postman resulst in an ECONN_RESET error. I am no networking expert, but i believe this error has to do with the fact that the application is protected by GLobalProtect and there is more communication necessary with the server to make it accept my modified http requests.
Is there anyone with knowledge about networking and GlobalProtect that could point me in the right direction towards setting up a direct communication with the server? Thanks so much!
I got this error in nginx error log:
SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking
I use Let's Encrypt currently. Any ideas to solve this problem? Thank you, guys.
This isn't your problem.
The best thing you can do in this situation is just to keep your server reasonably updated and secured.
At best for you, the client side of a request was running seriously outdated software, and at worst your server is simply being scanned for vulnerabilities by compromised devices connected to the internet.
Personally I lean in the direction of this being scanning, as I myself see these errors on a private development server, to which only I should ever have a legitimate reason to connect to, yet I see a ton of IP addresses mentioned by the error from around the world.
Similar question and answer has already been provided here:
https://serverfault.com/questions/905011/nginx-ssl-do-handshake-failed-ssl-error1417d18cssl/905019
Stay safe.
I was getting a similar error when I sent an HTTPS request from my computer in Iran to my server outside of Iran. Eventually I came to the conclusion that the problem is with our internet network (maybe government filtering) and using vpn solved the problem.
Therefore, I recommend testing with vpn.
Check your secrete key decoupling with other settings.ini file
your app secret is not linking with variable you set
This may sound simple, but I was struggling with this issue because I was attempting to access http://example.com instead of https://example.com. It probably isn't your issue - but it worked for me.
I have been researching on the concept of how event logs are collected from cloud based applications like dropbox without deploying agents...i haven't found any clear explanation based on this...it would be grateful if someone could explain.
This is a very broad topic and can be very confusing because everyone logs differently, so while i cannot answer the question definitively, I can hopefully help you along.
A good heuristic is to see if the cloud service supports one of the oldest logging standard, Syslog. Typically if they do, you will not need to deploy an agent, but configure log forwarding and listen for messages on Linux server you control (which already has a logging service running though it might need additional configuration). Also if the cloud service has a Syslog service running on the remote service, you potentially can use that service to forward logs to your Syslog server.
The mechanism used for transportation should be TLS because logs can unknowingly contain very sensitive data (Twitter just recently put out a security warning concerning this). You can see how to configure a Linux Syslog server with TLS here
I'm trying to import all my stuff from videomarathon.com/dk to videomarathon.com/se (posts etc.)
I'm using wordpress importer.
When uploading the exported file, it shows me this error:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 1333795156
Varnish cache server
Does anyone know what it means?
Is there anyone who might know another plugin for importing?
I'm using multiple sites, so maybe that's an issue?!
Thanks!
HTTP Error 503 - Service unavailable
The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.
503 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '503'.
Fixing 503 errors
The Web server is effectively 'closed for repair'. It is still functioning minimally because it can at least respond with a 503 status code, but full service is impossible i.e. the Web site is simply unavailable. There are a myriad possible reasons for this, but generally it is because of some human intervention by the operators of the Web server machine. You can usually expect that someone is working on the problem, and normal service will resume as soon as possible.
Please contact the system operators of the Web site (e.g. your ISP) to determine why the service is down. They will be in a much better position to help you than we are for this type of error.
Talk to your web host; it's an error at your web host one.com. The WP import plugin will work fine once the host problems are fixed.
And there's already an answer here to the same quesiton: Varnish: Guru Meditation
I'm using .netCHARGE (http://www.dotnetcharge.com/) to process credit cards and I'm getting the error: "TrustFailure: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." everytime I try to process a payment. I read through previous SO posts that match this error and have tried the SSL Diganostics Tool, but now I'm unsure what the problem could be.
.netCHARGE is just a dll in the /Bin directory, do I need to do something particular to this to allow it to use the site's SSL certificate?
Help appreciated. :)
For future reference to other SO users; this was caused by the receiving bank, not a problem with IIS, .netCHARGE or the code. The bank was refusing the traffic due to the account setup.