Cyberduck Mountain Duck CLI

#8372 closed defect (fixed)

Null pointer loading keys from

Reported by: joeatsalot Owned by: yla
Priority: high Milestone: 4.6.1
Component: s3 Version: 4.6
Severity: blocker Keywords: S3
Cc: Architecture: Intel
Platform: Windows 7


When connecting to S3, the connection fails immediately. In cyberduck 4.5.n this caused a complete app crash, but in 4.6 it just appears to do nothing.

  • Click Open Connection or create a bookmark
  • enter AWS Access Key ID and Secret Access Key
  • click Connect
  • the status bar flashes a message very briefly, but nothing else seems to happen

The log file shows the error:

[background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
	at IKVM... etc...

(log file attached)

As a result I'm completely unable to use (the awesome) Cyberduck for connecting to S3.

Attachments (1)

cyberduck - Copy.log (47.2 KB) - added by joeatsalot on Nov 26, 2014 at 9:35:30 PM.

Download all attachments as: .zip

Change History (7)

Changed on Nov 26, 2014 at 9:35:30 PM by joeatsalot

comment:1 Changed on Nov 26, 2014 at 9:37:36 PM by dkocher

  • Milestone set to 4.6.1
  • Owner changed from dkocher to yla
  • Summary changed from Fatal Key Store error connecting to S3 to Null pointer loading keys from

comment:2 Changed on Nov 27, 2014 at 1:13:22 PM by dkocher

2014-11-27 09:56:44,205 [background-1] INFO  ch.cyberduck.core.ssl.CertificateStoreX509KeyManager - Load default store of type Windows-MY
2014-11-27 09:56:44,268 [background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
	at IKVM.Runtime.JNIEnv.StringFromUTF8(Unknown Source)
	at IKVM.Runtime.JNIEnv.NewStringUTF(Unknown Source)
	at Method)
	at ch.cyberduck.core.ssl.CertificateStoreX509KeyManager.init(
	at ch.cyberduck.core.ssl.CertificateStoreX509KeyManager.<bridge>init(
	at ch.cyberduck.core.ssl.SSLSession.getKeyManager(
	at ch.cyberduck.core.http.HttpSession.registry(
	at ch.cyberduck.core.http.HttpSession.builder(
	at ch.cyberduck.core.s3.S3Session$RequestEntityRestStorageService.<init>(
	at ch.cyberduck.core.s3.S3Session.connect(
	at ch.cyberduck.core.s3.S3Session.<bridge>connect(
	at ch.cyberduck.core.LoginConnectionService.connect(
	at ch.cyberduck.core.LoginConnectionService.check(
	at ch.cyberduck.core.LoginConnectionService.check(
	at ch.cyberduck.core.threading.SessionBackgroundAction.connect(
	at ch.cyberduck.ui.threading.BrowserBackgroundAction.connect(
	at ch.cyberduck.ui.AbstractController$
	at java.util.concurrent.FutureTask$Sync.innerRun(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
	at ch.cyberduck.core.threading.NamedThreadFactory$

comment:3 Changed on Nov 28, 2014 at 1:32:57 PM by yla

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r15888.

comment:4 Changed on Dec 3, 2014 at 3:04:21 AM by joeatsalot

Woohoo! That was quick. I'm looking forward to 4.6.1.


comment:5 Changed on Dec 3, 2014 at 7:54:32 AM by dkocher

Please update to the latest snapshot build available and let me know if the issue is resolved.

comment:6 Changed on Dec 3, 2014 at 8:22:38 PM by joeatsalot


Thank you very much.

Note: See TracTickets for help on using tickets.