Since my HP EliteDesk 800 is not an option for me due to the problem with the Intel LAN connection for the eBlocker4, I switched to a new (used) thin client (Lenovo ThinkCentre M75n with Ryzen 3 Pro 3300U, 8GB and 128 GB SSD).
First, I used eBlocker3 on this hardware for three weeks to have a basis for comparison.
With eBlocker 4.0.2, I observed the following issues.
Threema: does not connect initially (red line). Only after briefly disabling HTTPS activation for the smartphone does the connection work and remain active with HTTPS activation until the next new network connection. Manual logging of the HTTPS connection did not result in any entries, and HTTPS connection errors were not displayed either.
Feeder: The preview images on the right side of the feeder are initially filled with placeholders only. The preview images appear gradually (20–40 seconds).
Tusky: Some of the preview images are displayed as placeholders only.
I hope my description is clear enough.
In general, I have the impression (compared to eBlocker3) that eBlocker4 is “sluggish.”
Thank you for the report!
That is strange: Threema on iOS works without any problems with my test eBlocker 4.0.3, but the Android app does not want to connect (red line).
I have enabled the Threema HTTPS exception list, so threema.ch and all its sub-domains are whitelisted.
There is a debug log option in Threema's settings at Settings / About Threema / Advanced Options / Logging. But the error is not really shown in the log:
INFO ThreemaApplication: ServerConnection state changed: CONNECTING INFO ServerConnection.CspSocket: Connecting to g-a0.0.threema.ch/203.56.112.204:443 ... INFO ProxyAwareSocketFactory: No proxy configured INFO ThreemaApplication: ServerConnection state changed: CONNECTED INFO ConnectionLock.PURGE_INCOMING_MESSAGE_QUEUE: Acquiring lock #76 with 60.00s timeout INFO ServerConnection.CspSocket: Reading stopped INFO ServerConnection.CspSocket: Writing stopped WARN ServerConnection.BaseSocket: IO processing stopped exceptionally java.io.EOFException...
The server (or the proxy on the eBlocker) just seems to close the connection.
I will have to do some network level debugging with Wireshark...