Feature Request - Built in UI Based Geoblock Rule #512

New Issue

GiteaMirror · 2025-11-13T12:02:58-06:00

GiteaMirror commented

2025-11-13 12:02:58 -06:00

Originally created by @urchin967 on GitHub (Jul 21, 2025).

Feature Request: Built-in UI-Based Geoblock Rule

Hi Dev Team,

First off, thank you for all the hard work and continuous improvements you’ve been making to the platform — it’s much appreciated!

I’d like to request a feature that would significantly enhance both security and ease of use:
A built-in, UI-based geoblock rule configuration panel.

⸻

Description:
Please consider adding a native interface that allows users to easily set up geolocation-based access control rules. The feature could include:
• A multi-select dropdown UI to select countries/regions
• The ability to allow or deny traffic from specific locations
• IP geolocation database integration (MaxMind, IP2Location, etc.)
• Optional logging or alert system for blocked attempts

⸻

Why This Matters:
I attempted to implement geoblocking using a Traefik plugin, but ran into critical issues. Specifically, the plugin caused the reverse proxy to break with the following error:

connection failed to decode token response: json cannot unmarshal number into go value type websocket.token response

This was a major disruption and took time to troubleshoot. It underscored the need for a more stable, officially supported, and UI-integrated way to handle geoblocking.

Having this built-in would make things much more accessible and reduce risk for users who are not deeply familiar with Go, Traefik plugins, or manual JSON handling.

Thanks again for your time and dedication!

Best regards,
Urchin

Originally created by @urchin967 on GitHub (Jul 21, 2025). Feature Request: Built-in UI-Based Geoblock Rule Hi Dev Team, First off, thank you for all the hard work and continuous improvements you’ve been making to the platform — it’s much appreciated! I’d like to request a feature that would significantly enhance both security and ease of use: A built-in, UI-based geoblock rule configuration panel. ⸻ Description: Please consider adding a native interface that allows users to easily set up geolocation-based access control rules. The feature could include: • A multi-select dropdown UI to select countries/regions • The ability to allow or deny traffic from specific locations • IP geolocation database integration (MaxMind, IP2Location, etc.) • Optional logging or alert system for blocked attempts ⸻ Why This Matters: I attempted to implement geoblocking using a Traefik plugin, but ran into critical issues. Specifically, the plugin caused the reverse proxy to break with the following error: connection failed to decode token response: json cannot unmarshal number into go value type websocket.token response This was a major disruption and took time to troubleshoot. It underscored the need for a more stable, officially supported, and UI-integrated way to handle geoblocking. Having this built-in would make things much more accessible and reduce risk for users who are not deeply familiar with Go, Traefik plugins, or manual JSON handling. Thanks again for your time and dedication! Best regards, Urchin

GiteaMirror closed this issue

2025-11-13 12:02:58 -06:00

GiteaMirror commented

2025-11-13 12:02:59 -06:00

@Crashman1983 commented on GitHub (Jul 21, 2025):

oh yes. GeoIP-Shell might work well, but a UI based and easy to use approach would be fine!

@Crashman1983 commented on GitHub (Jul 21, 2025): oh yes. GeoIP-Shell might work well, but a UI based and easy to use approach would be fine!

GiteaMirror commented

2025-11-13 12:02:59 -06:00

@oschwartz10612 commented on GitHub (Jul 22, 2025):

Thanks so muck for taking the time to post a suggestion! This has been hotly requested and I think we will tackle soon! I am going to close this because I think there is already a couple of requests in the discussions.

https://github.com/orgs/fosrl/discussions/769

@oschwartz10612 commented on GitHub (Jul 22, 2025): Thanks so muck for taking the time to post a suggestion! This has been hotly requested and I think we will tackle soon! I am going to close this because I think there is already a couple of requests in the discussions. https://github.com/orgs/fosrl/discussions/769

GiteaMirror referenced this issue

2026-04-16 09:10:36 -05:00

[GH-ISSUE #2349] Feature Request: Native/Kernel WireGuard support for Newt with full site-to-site networking #2147

GiteaMirror referenced this issue

2026-04-20 08:31:56 -05:00

[GH-ISSUE #2349] Feature Request: Native/Kernel WireGuard support for Newt with full site-to-site networking #4089

GiteaMirror referenced this issue

2026-04-25 15:56:15 -05:00

[GH-ISSUE #2349] Feature Request: Native/Kernel WireGuard support for Newt with full site-to-site networking #6943

GiteaMirror referenced this issue

2026-04-30 05:01:37 -05:00

[GH-ISSUE #2349] Feature Request: Native/Kernel WireGuard support for Newt with full site-to-site networking #8911