cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Can't add URL to webhook URI.

Can't add URL to webhook URI.

harshap
Helpful | Level 6
Go to solution

I am not able to add "https://www.tarrison.com:8443/webhook/dropbox" to webhook section in dropbox application and one popup shows up and say "There was a problem completing this request." on other hand I just remove https and start server on http ,
I am able to add 'http://www.tarrison.com:8080/webhook/dropbox'. 
So I need to know why this happening and How to fix it.

2 Accepted Solutions

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

Thanks for the report! It looks like we may be having trouble connecting to your webhook URI with your TLS configuration. We'll look into it. 

As a few potential workarounds, can you try:

View solution in original post

Greg-DB
Dropbox Staff
Go to solution

The reported error would be: "unable to get local issuer certificate". Trying directly in curl looks like:

$ curl -v "https://www.tarrison.com:8443/webhook/dropbox?challenge=6TV4oooNb9AnHM5vEK6qQw_yXE1dNNWQrcau-UY_YO8"
*   Trying 35.182.122.11...
* Connected to www.tarrison.com (35.182.122.11) port 8443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 594 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
* Closing connection 0
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

That seems to indicate an issue with the certificate or chain your server is being served with. The SSL Labs test does indicate some certificate/chain issues, so I recommend resolving those, or switching to a different certificate entirely.

View solution in original post

5 Replies 5

Greg-DB
Dropbox Staff
Go to solution

Thanks for the report! It looks like we may be having trouble connecting to your webhook URI with your TLS configuration. We'll look into it. 

As a few potential workarounds, can you try:

Greg-DB
Dropbox Staff
Go to solution

We've looked into this more, and confirmed that the issue is that the verification connection to your webhook URI is failing due to the TLS issues. 

Additionally, we then are not correctly displaying the error information on the app page, which causes the generic error message. We'll work on fixing the error handling so that the actual error is reported back properly.

harshap
Helpful | Level 6
Go to solution

Thanks Greg,

Can you explain or write error you have got??
Application is running in production mode so I can't remove https and port because we have two diffrent application on same domain with different port.

If there is any other work arounds let us know.

Greg-DB
Dropbox Staff
Go to solution

The reported error would be: "unable to get local issuer certificate". Trying directly in curl looks like:

$ curl -v "https://www.tarrison.com:8443/webhook/dropbox?challenge=6TV4oooNb9AnHM5vEK6qQw_yXE1dNNWQrcau-UY_YO8"
*   Trying 35.182.122.11...
* Connected to www.tarrison.com (35.182.122.11) port 8443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 594 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
* Closing connection 0
curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

That seems to indicate an issue with the certificate or chain your server is being served with. The SSL Labs test does indicate some certificate/chain issues, so I recommend resolving those, or switching to a different certificate entirely.

harshap
Helpful | Level 6
Go to solution

Thanks Greg,

We resolve the issue.
We didn't add certificate chain in our server. After adding that "https://www.tarrison.com:8443/webhook/dropbox"  added to webhook URI.

Need more support?