Cyberduck Mountain Duck CLI

#9796 closed defect (worksforme)

Connection failure with timeout

Reported by: bryanjb Owned by: bryan
Priority: highest Milestone:
Component: b2 Version: 5.2.2
Severity: critical Keywords:
Cc: Architecture: Intel
Platform: Windows 10

Attachments (1)

Untitled.jpg (62.3 KB) - added by thibaultmol on Dec 27, 2016 at 6:00:59 PM.

Download all attachments as: .zip

Change History (9)

Changed on Dec 27, 2016 at 6:00:59 PM by thibaultmol

comment:2 Changed on Dec 27, 2016 at 8:43:58 PM by dkocher

  • Component changed from core to b2
  • Summary changed from connection failed to Connection failure with timeout

comment:3 Changed on Dec 27, 2016 at 8:44:23 PM by dkocher

  • Description modified (diff)

comment:4 Changed on Dec 27, 2016 at 8:44:52 PM by dkocher

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

Please contact Backblaze B2 support about this service availability problem.

comment:5 Changed on Jan 5, 2017 at 7:11:57 AM by thibaultmol

  • Resolution thirdparty deleted
  • Status changed from closed to reopened

I contacted Backblaze support and Anthony just responded with the following:


My apologies for the delay. Are you still seeing these errors? 

If so, I don't mean to keep handing you back and forth but there doesn't appear to be an issue on our end. Our availability is normal. We also haven't had other users writing in about connection issues for B2 through any other means or from Cyberduck. Cyberduck also appears to be working normally for me and others at Backblaze.


comment:6 Changed on Jan 5, 2017 at 8:35:58 AM by thibaultmol

Weird. I just tried it on the mac mini but only connected to the wifi hotspot of my iphone (acting as a mobile hotspot). Then it does seem to work...

So I'm thinking it had something to do with my internet. I've used B2 in Cyberduck without port forwarding before.

Just as a test though I tried to port forward port 443 to my ip but it still doesn't work. Any other ideas?

comment:7 Changed on Jan 9, 2017 at 10:04:14 AM by dkocher

  • Resolution set to worksforme
  • Status changed from reopened to closed

It looks like a connectivity issue from your computer possibly caused by a firewall or malfunctioning router in between.

comment:8 Changed on Sep 8, 2021 at 9:43:23 PM by thibaultmol

  • Description modified (diff)
Note: See TracTickets for help on using tickets.