Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to transfer files to NetApp StorageGRID with self-signed certificate #11635

Closed
cyberduck opened this issue Mar 26, 2021 · 1 comment
Closed

Unable to transfer files to NetApp StorageGRID with self-signed certificate #11635

cyberduck opened this issue Mar 26, 2021 · 1 comment
Assignees
@dkocher
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

4e1a275 created the issue

Attempting to use version 7.8.3 to connect to a StorageGRID environment that is using a self-signed certificate valid until 2038. Upon attempt to transfer, I get a prompt to accept the certificate, sometimes multiple times. Selecting "Always Trust" does not appear to have an effect. Listings all fail without error. Uploads fail with 0 bytes transferred.

I installed the CLI and enabled debug logging (attached). I picked Windows 8.1 as our platform, but this software is installed on Windows 2012R2 through our enterprise license agreement.

My team runs a lab service for our employees, partners, and customers. I can offer direct access to copies of this lab environment with StorageGRID installed and running for diagnosis.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

It looks like there is an interoperability issue with the versioning response from Netapp. It would be very helpful if you can provide a temporary test account. Please write to [mailto:support@cyberduck.io].

[background-2] INFO  ch.cyberduck.transcript.request - GET /?versioning HTTP/1.1
[background-2] INFO  ch.cyberduck.transcript.request - Date: Fri, 26 Mar 2021 19:59:38 GMT
[background-2] INFO  ch.cyberduck.transcript.request - x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649
b934ca495991b7852b855
[background-2] INFO  ch.cyberduck.transcript.request - Host: demo.dc1-g1.demo.netapp.com
[background-2] INFO  ch.cyberduck.transcript.request - x-amz-date: 20210326T195938Z
[background-2] INFO  ch.cyberduck.transcript.request - Authorization: ********
[background-2] INFO  ch.cyberduck.transcript.request - Connection: Keep-Alive
[background-2] INFO  ch.cyberduck.transcript.request - User-Agent: Cyberduck/7.8.3.34411 (Windows 8.1/6.3) (amd64)
[Thread-0] INFO  ch.cyberduck.core.threading.DefaultBackgroundExecutor - Scheduled background runnable WorkerBackgroundA
ction{worker=SessionListWorker{directory=Path{path='/demo', type=[file]``` for execution
[background-2] INFO  ch.cyberduck.transcript.response - HTTP/1.1 200 OK
[background-2] INFO  ch.cyberduck.transcript.response - Date: Fri, 26 Mar 2021 19:59:38 GMT
[background-2] INFO  ch.cyberduck.transcript.response - Connection: KEEP-ALIVE
[background-2] INFO  ch.cyberduck.transcript.response - Server: StorageGRID/11.3.0
[background-2] INFO  ch.cyberduck.transcript.response - x-amz-request-id: 1616788777533753
[background-2] INFO  ch.cyberduck.transcript.response - x-amz-id-2: 12580019
[background-2] INFO  ch.cyberduck.transcript.response - Content-Length: 491
[background-2] INFO  ch.cyberduck.transcript.response - Content-Type: application/xml
[background-2] DEBUG org.apache.http.impl.execchain.MainClientExec - Connection can be kept alive indefinitely
[background-2] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Response for 'GET'. Content-Type: appl
ication/xml, Headers: [Date: Fri, 26 Mar 2021 19:59:38 GMT, Connection: KEEP-ALIVE, Server: StorageGRID/11.3.0, x-amz-re
quest-id: 1616788777533753, x-amz-id-2: 12580019, Content-Length: 491, Content-Type: application/xml]
[background-2] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Response entity: ResponseEntityProxy{[
Content-Type: application/xml,Content-Length: 491,Chunked: false]}
[background-2] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Entity length: 491
[background-2] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Received response code 200; matches on
e of expected set ([200])? true
[background-2] DEBUG org.jets3t.service.impl.rest.XmlResponsesSaxParser - Parsing XML response document with handler: cl
ass org.jets3t.service.impl.rest.XmlResponsesSaxParser$VersioningConfigurationHandler
[background-2] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection [id: 1][route: {s}->https
://demo.dc1-g1.demo.netapp.com:8082] can be kept alive indefinitely
[background-2] DEBUG org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-1: set socket timeout
to 0
[background-2] DEBUG org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection released: [id: 1][route:
{s}->https://demo.dc1-g1.demo.netapp.com:8082][total available: 2; route allocated: 1 of 10; total allocated: 2 of 21474
83647]
[background-2] DEBUG org.jets3t.service.impl.rest.httpclient.HttpMethodReleaseInputStream - Released HttpMethod as its r
esponse data stream is fully consumed
[background-2] WARN  ch.cyberduck.core.threading.BackgroundCallable - Failure java.lang.NullPointerException running bac
kground task

}}}

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck