Update error on Version: 5.143 (2025012904)

Based on BTT Clipboard Manager Development & Wishlist I guess you released new version, but when I check the main or alpha update channels I get "Update error. An error occurred in retrieving update
information. Please try again later."

BTT was restarted (also quit and start) few time without any luck.

when did you check? I did some server maintenance until about ~20 min ago but it should all be back online now

Right prior creating the topic. I've also checked now - still the same.

Weird, maybe something is still cached somewhere, but I can see quite a few updates happening right now.
Does it show that message right when you check for updates? Or does it first show the release notes screen?

No, it is checking for update for some seconds and then it shows the error. No "Release notes screen"

Could it be a firewall issue? Just tried in my VM, but it's also working fine there

For some reason, using my ISP connection without a VPN, folivora.ai and some sub-domains , e.g. "updates.folivora.ai" are not reachable , however the "community.folivora.ai" is, but I guess this is because they are on different machines or at least behind different public IPs, while folivora.ai and updates.folivora.ai are behind the same IP - 78.46.5.187.

I can confirm that this is not a machine/firewall issue since I've tested from two more devices connected to the same network - the results are the same. If I use my 4G/5G cellular network everything is working.

There is ping/ICMP connectivity to 78.46.5.187, traceroute from a working network and non-working one are or or less the same, last hop shown is ex9k2.dc1.nbg1.hetzner.com (213.239.203.218) 36.551 ms 33.754 ms

Can you check if there are requests hitting your servers, load balancers etc. from my public IP (I'll share it via DM if you are OK)?

You are correct community.folivora.ai is hosted on a different server and I think even different datacenter from Hetzner.

Does it resolve to the ip when you ping? So no DNS issue? Then it is most likely a routing issue between hetzner and your provider. I can report this to Hetzner, it has happened a few times over the last 15 years. Could you send me your provider name via PN? They say if I provide the traceroute that can help them fix it faster, so if you can include that, would be great!

I checked via a few of these "is this site down only for me?" checkers - they show the sites as available, so it doesn't seem to be a general issue at least. Often these things only affect specific providers

In case you want to download manually for now you can try whether my download server is reachable:
https://bttreleases.llo.ai/btt5.147-2025012908.zip

Or you can use this forum based link (I use the forum server to load balance some of the update traffic)
https://community.folivora.ai/uploads/short-url/p0jIFQOBBjfJPlQFSAAOhcwu9qE.zip

No DNS issue, dig/nslookup are resolving and reverse-resolving correctly.

I've sent a DM with the details. The interesting part is that a friend of mine on the same ISP does not have this issue, but another one have it.

Thanks for the download server - it is accessible.

Just to be sure it's not a issue with the machine, there is no entry in your hosts file that might affect this? is folivora.ai accessible from your phone?

sudo nano /etc/hosts

Yep, it is not a device issue, like mentioned:

I can confirm that this is not a machine/firewall issue since I've tested from two more devices connected to the same network - the results are the same. If I use my 4G/5G cellular network everything is working.

1 Like

and probably also no recent changes to your router?

Very weird issue, I'll ask Hetzner!

Yep, no changes on the router, I even restarted it before reporting. It is a provider issue 99%, because a friend of mine on the same ISP is also facing this.

1 Like

Thanks a lot for the details I have created a support request at Hetzner, they are usually quick to resolve things.

1 Like

Hey Andreas, I think this is resolved now.

great!

Can you confirm if Hetzner did something on their end?

I’m not sure what they did but they closed the ticket as resolved