Active-session badge on blocked IPs
A blocked address now shows an active-session badge only when there is really a live connection from that address, so the blocklist tells the whole story.
HearthGate 1.13 is live
Blocked IPs no longer stay quiet when they are still connected.
HearthGate 1.13 closes a subtle visibility gap in IP blocking. When an address you block by hand, or one HearthGate blocks after repeated failed logins, still has a live session open, HearthGate now shows that state directly and gives you a one-click way to disconnect it.
One-click disconnect from the blocklist
Use the new Disconnect action on a blocked entry to end live sessions from that address, with a precise report of how many sessions were closed.
Clearer security-event logging
System events can now record when a newly blocked IP is still connected and when the new disconnect action closes those sessions.
Automatic update path
No manual steps are required. Relaunch HearthGate and the refreshed helper brings the new blocklist behavior online automatically.
Blocklist visibility
Blocking stops the next attempt. 1.13 shows what is already inside.
An IP block is meant to stop new connections. Existing sessions are a different state, and hiding that state creates confusion. HearthGate 1.13 makes the difference visible: blocked does not mean invisible, and visible means you can act.
Operator control
Manual blocks get live context
If you block an address while it is still connected, HearthGate surfaces the active session instead of leaving you to wonder why the screen is still up.
Security banner
Auto-blocks raise a signal
When repeated failed logins trigger an automatic block and that address still has a live session, the in-app security banner can alert you immediately.
Audit clarity
Disconnect reports what changed
The disconnect action reports the number of sessions it closed, making the result understandable for operators and useful in later review.
Operational examples
Where 1.13 removes the guesswork
The new behavior is small on the surface, but it matters when you are reacting to a suspicious source IP and need the UI to match reality.
Use case
You block a noisy IP by hand
The blocklist entry shows when that address still has an active session, and gives you a direct Disconnect action for that source.
Use case
Brute-force protection blocks an address
If the same address already has a live session, HearthGate raises the state in the app instead of treating the block as the end of the story.
Use case
You need proof of what changed
System events can record both the discovery of an active session from a blocked IP and the number of sessions closed by the operator.
Use case
A block should not feel ambiguous
Blocking still stops new connections. 1.13 adds the missing operator view for sessions that were already established.
Security notes
1.13 makes blocked-source state visible, actionable, and reviewable.
This release keeps IP blocking honest. It does not pretend an established session disappeared simply because the source address is now blocked; it shows the remaining live state and lets the operator close it.
Learn about SILA, the codnamacs security lifecycle frameworkRelease notes at a glance
- Blocked IP entries can show an active-session badge when a live session from that address is still open.
- A one-click Disconnect action on the blocked entry can close those live sessions.
- Disconnect reports exactly how many sessions were closed.
- System events can record when a freshly blocked IP is still connected.
- System events can also record how many sessions were closed by the blocked-IP disconnect action.
- The in-app security banner can alert you when a blocked source is still connected.
- The badge only appears when HearthGate can see a real active session from that address.
- Updates are automatic after relaunch, with no manual setup steps.
HearthGate 1.13