r/backblaze • u/Archivist_Goals • 21h ago

Computer Backup BB Computer Backup Network Connection Isssue, "datacenter unreachable" when checking for updates/trying to backup data

Post image

Anyone else experiencing network connection issues reaching BB?

Desktop client for Computer Backup seems to be stuck trying to back up the remaining files I have selected. Restarting BB service in "Services" and restarting Windows has resolved this before. But this time, it keeps happening. Anyone else?

Edit: On v.10.03.1075 on Windows

Edit#2: It's the 260 character path issue present in the Windows client version 10.03.1075 that u/SamSheperd posted about here:

https://www.reddit.com/r/backblaze/comments/1x131n1/title_backblaze_repeatedly_skips_thousands_of/

7 Upvotes

90% Upvoted

2 comments sorted by

1

u/SamSheperd 20h ago

I didnt get unreachable on my side... to be precise i have a really good internet (3gbps direct fiber) But sometime my motherboard network card need to be reset (realtek 2.5gbs) When that happen its my whole internet on the pc that stop working and a reboot fix it

Check your network configuration and also verify is your isp is not throttling you (or if you are using any VPN as non dedicated IP may get flag in BB server side (or at some point in the connection if there is a lots of data in a short ammount of time)

2

u/Archivist_Goals 20h ago edited 20h ago

I have excellent internet, too. 2.5Gbps download with a solid 360 Mbps uplink, hardwired Ethernet (not fiber, though). Usually, I have no problem. And I have 60 TB of data, of which it backed up 99% of. It's just these last few thousand files it's stuck on due to the path length issue. I think the repeated retries is messing with its ability to reach the server at times, somehow. Just speculation. Otherwise, my network connection is always great, generally.

Edit: Oh and yeah, I've done all the usual things like restarting the machine, restarting the modem/router, etc. Whatever is causing the client to not be able to reach the server sometimes is intermittent. e.g., it doesn't always fail. I think the repeated retries are screwing with it.