eBlocker Open Source Forum - Recent Posts

RE: Threema App not working any more with eBlocker enabled

mr.bien — Thu, 10 Sep 2026 11:02:01 +0000

Great, thank you!

RE: Threema App not working any more with eBlocker enabled

Boris — Thu, 10 Sep 2026 09:31:46 +0000

You can keep your modified trusted app. When the updated list is installed, eBlocker will show that the Threema app is locally modified. You can then "reset" the app to get the updated built-in app.

RE: Threema App not working any more with eBlocker enabled

mr.bien — Thu, 10 Sep 2026 09:14:39 +0000

I have added Threema's IP range 203.56.112.0/23 to the trusted app. (Will be in the next lists update that will be built tomorrow morning.)

One question on this. I added that IP also to my Threema-App. Shall I remove that in order to take over the changed list update? In other words: is there something I need to take into account when taking over the list from the built?

RE: Threema App not working any more with eBlocker enabled

Boris — Thu, 10 Sep 2026 07:26:49 +0000

Thank you for testing!

I have added Threema's IP range 203.56.112.0/23 to the trusted app. (Will be in the next lists update that will be built tomorrow morning.)

I hope that Threema's other message servers are in that range, too.

RE: Threema App not working any more with eBlocker enabled

mr.bien — Thu, 10 Sep 2026 03:35:44 +0000

I tried this as well - seems to work now again. Thank you for your support!

RE: Threema App not working any more with eBlocker enabled

Error404 — Wed, 09 Sep 2026 22:46:44 +0000

Thanks for the tip, I can confirm this!

In my case, the app requested g-70.0.threema.ch, which resolved to the exact same IP address: 203.56.112.202.

After adding this IP to the Threema trusted app entry in the HTTPS settings, Threema works properly again even with HTTPS inspection enabled.

Thank you!

RE: Threema App not working any more with eBlocker enabled

Boris — Wed, 09 Sep 2026 19:23:42 +0000

I tried adding the server's IP address to the Threema trusted app in eBlocker's HTTPS settings and it seemed to help.

I saw in Wireshark that the app sent DNS requests for g-39.0.threema.ch which resolved to 203.56.112.202. I added this IP to the trusted app and the Threema app connected.

Can anyone confirm that?

(Maybe your Threema app tries other domains. The Personal Device Firewall recording in eBlocker's dashboard can help.)

RE: Threema App not working any more with eBlocker enabled

Error404 — Tue, 08 Sep 2026 21:00:11 +0000

can confirm the exact same issue.
My setup:

eBlocker version: 3.2.3
iPhone iOS 26.6.1 (Threema App 7.3.3) – experiencing the problem.
iPhone iOS 18.3.1 (Threema App 4.8.3) – working without any issues.

In my experience, this started with version 7.x / 7.3. Prior to that, Threema worked seamlessly with eBlocker.
The problem is tied directly to eBlocker’s HTTPS inspection: when HTTPS scanning is active for the device, Threema fails to send and receive messages. As soon as I disable HTTPS interception for the iPhone, Threema works normally again.

with https:

1734

without https:

1735

RE: Threema App not working any more with eBlocker enabled

mr.bien — Mon, 07 Sep 2026 18:04:52 +0000

”Nice“ to hear that I am not the only one facing this issue. ;-)

BTW, I am also using individual network settings.

RE: Threema App not working any more with eBlocker enabled

Boris — Mon, 07 Sep 2026 14:52:09 +0000

I have the same issue currently. Whitelisting domains does not help.

Push notifications are received, but new messages are not shown and a red line appears below the upper navigation bar.

I am wondering whether this has something to do with Threema's proprietary protocol. I looked into it last year with Android. But last year it seemed that at least port 5222 worked if eBlocker is DHCP.

(I am running eBlocker in individual network settings.)

Sorry, no solution yet, I have to look into it again.