Mir ist die Meldung unten im Brickv auf dem macMini aufgefallen. Weiß nicht, seit wann das da steht. Beim MacBook taucht sie nicht aus. Ich bin mir nicht bewusst dass ich etwas umkonfiguriert habe. Eine Idee? Ich finde nichts an Berechtigungen für Brickv ... Werde mal neu installieren

macMini M1, macOS 26.2, neuester Brickv 2.4.26, gerade noch mal installiert.

Cheers, Uwe

Same here with Brickv 2.4.24. Weird, because version files seem to be fine here and here. Maybe a code signing thing with Apple?

Update: it seems the developer certificate expired.

Completely removed Brickv 2.4.24 using Tinkertool → Rebooted → Installed Brickv 2.4.26 → Still the same problem.

Edited February 6, 2026 at 09:57 AMFeb 6, 2026 by Superp
Resized images

There are two different issues. We moved our servers to a new infrastructure and by doing that changed the root ca. Because of that brickv doesn't like to download from tinkerforge.com anymore. Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.

Hmm, I'm pretty sure I run the same version of Brickv on the same version of macOS in my office. There everything runs as expected.

This morning I pushed an update that enables the Tinkerforge Ruby bindings to check firmware versions. To my surprise it immediately found a Bricklet with outdated firmware.

For now it expects you to download latest_versions.txt yourself and put it in either ~/.config/tinkerforge/downloads or /etc/tinkerforge/downloads

This is still somewhat experimental, your kilometrage may vary, etc. Feel free to port this code to your favourite programming language.

Edited February 13, 2026 at 08:08 PMFeb 13, 2026 by Superp
Restored disappearing screenshot

Am 6.2.2026 um 11:23 schrieb borg:

Because of that brickv doesn't like to download from tinkerforge.com anymore.

Please forgive my ignorance. Wouldn't that affect every running brickv running in the world out there? But on my Laptop I do not see this message.

Am 6.2.2026 um 11:23 schrieb borg:

Additionally we need to renew the developer cert for the next brickv release, but that is a different issue.

I hate this traffic sign. Any idea when that release will come?

I cannot reproduce the download issue here, with two different MacBooks with macOS 15.5 and 26.1.

It's not a general issue with our server, but with Python not being able to verify the HTTPS certifcate of our server. We are using Let's Encrypt now. I'm a little puzzled why it should not work. I suspect a problem local to the affected computer.

Could you try running this terminal command on the affected computer and post it's output here:

curl -v https://download.tinkerforge.com

Same with Python please:

python3 -c "from urllib.request import urlopen; print(urlopen('https://download.tinkerforge.com').read()[:100])"

Yes, the code signing certificate used to sign that version of brickv is expired by now. But that's not a real issue, because the signature is timestamped and at the time brickv was signed the certificate was valid. This version of brickv is still properly signed. There is no issue to be fixed. There will not be a new brickv release just because of that. Apple decided to show this in a too dramatic way, making it look like an issue. This also has nothing to do with the download issue.

Files attached.

curl.txt python.txt

What I wanted to see is not in the curl log file because you only redirected stdout to the log file.

Please run this command:

curl -v https://download.tinkerforge.com &> curl.txt

But both logs already show that the download is working.

On 2/16/2026 at 3:43 PM, photron said:

Apple decided to show this in a too dramatic way, making it look like an issue.

Hold your horses. That is not what happened. I ran into the above problem with Brickv and tried finding the cause. I did some digging and found your developer cert expired a few months ago. That's it: I did some digging.

The expired developer certificate worries me a bit whether it is causing this trouble or not, but that is a different conversation.

The URL "https://download.tinkerforge.com/latest_versions.txt" works fine with Safari, Curl, Wget, Python3, Ruby, and also Shortcuts. URL https://download.tinkerforge.com/ works too.

Brickv reports an error.

This is stderr for curl -v https://download.tinkerforge.com/latest_versions.txt 2> curl_stderr.txt :

curl_stderr.txt

As I cannot reproduce the problem here I need help. Could anyone that is affected by the download problem run this brickv Github branch from source in a terminal? It prints the exception backtrace to the terminal. I would like to see this backtrace.

GitHub

GitHub - Tinkerforge/brickv at macos-download-problem

Small Qt GUI to control and test all Bricks and Bricklets from Tinkerforge - GitHub - Tinkerforge/brickv at macos-download-problem

I am willing to try, and have checked out that branch. However, I have no experience with the Python toolchain and so far have not succeeded in getting this running. I'll try again later.

python seem to be slightly different on both machines. I am not a python person. I probably messed up python on the Mac mini while it is ok for Brickv on the MacBook Pro.
There is Python 2.7.18 (python --version, /opt/homebrew/bin/python2) and Python 3.14.3 (python3 --version, /opt/homebrew/bin/python3) on both machines. Probably python installations are slightly different on both machines … But, honestly, I do not know what happens under the hood.

I, too, do not succeed to get the Brickv branch running.

@photron I have tried getting this version of brickv running. No success. I basically do not know what I'm doing trying to "fix" errors with Python.

Alternate approach: I have captured brickv's network traffic in a .pcap file, when it 1) Does a clean start 2) Fetches update data 3) Quits.

The pcap file is in your email. Maybe it is helpful.

On 2/19/2026 at 11:09 AM, Superp said:

The pcap file is in your email. Maybe it is helpful.

Thank you. I can see that connection fails with a certificate error. That's what I expected to be the problem.

Please try this test version of brickv. Either this one just works now, or it reports an error, that should help me to figure out what's wrong.

Edit: Obsolete brickv version removed.

It reports an error. Click "OK" and it immediately returns, 3 times in total. The dialog below immediately appears 3-fold, stacked on top of each other:

Edited February 19, 2026 at 01:47 PMFeb 19, 2026 by Superp
Correct/clarify

Same the messages here on the Mac mini w/ this version. And this version too runs flawlessly on the MacBook Pro (same OS) like the regular one.

Why is this behavior so different?

Edited February 20, 2026 at 02:29 PMFeb 20, 2026 by duaw

Okay, so brickv fails to validate the SSL certificate of download.tinkerforge.com, but every other program has no issue with it.

Please try this version. It adds details about the CA store used to validate the SSL certificate. I suspect that Python uses an empty CA store on some devices, but not on others.

On 2/19/2026 at 1:44 PM, Superp said:

The dialog below immediately appears 3-fold, stacked on top of each other

This is expected. It's a side effect of the specific way I added this error message.

Edit: Obsolete brickv version removed.

Am 23.2.2026 um 12:30 schrieb photron:

Please try this version. It adds details about the CA store used to validate the SSL certificate. I suspect that Python uses an empty CA store on some devices, but not on others.

This is expected. It's a side effect of the specific way I added this error message.

Same messages on my Mac mini w/ this version.

I bet this version of brickv runs fine on my MacBook Pro (as did all other previous versions of brickv on THAT machine). Don't have it her right now.

The last line of the error message shows that the CA store is really empty.

Here is a brickv version that tries to load the system CA store. This might actually fix the problem.

I removed the other error message again. There will be just one message box showing details about the load process. I'd like to see that one.

Edit: Obsolete brickv version removed.

Success! Thanks!

Strange.

Same msg & works here too.