How to Configure GeoIP to Block or Allow Countries on Your Servers
GeoIP lets you decide from which countries traffic is allowed or blocked to the public IPs of your services.
It's an easy way to reduce your attack surface when legitimate traffic should only come from specific regions.
π What you get
Control access to your services by country of origin, for each public IP, with a return to the default state in one click.
What it's for
Security: block regions from which you only receive attacks.
Simplicity: country-based rules, without keeping IP lists by hand.
Compliance: apply country restrictions if your client requires it (for example, GDPR or sector-specific requirements).
Flexibility: different policies per server or per network depending on the case.
How it works
GeoIP combines two layers:
Perimeter layer, at the edge of the infrastructure: filters traffic by country. This is where the global default policy lives (the list of blocked countries).
Your subscription's network layer: controls the ports and protocols of Inbound/Outbound within your network. It does not filter by country.
From GeoIP, for each public IP you choose the blocked countries: checked equals Deny and unchecked equals Allow, unless that country was already blocked by the global policy. If you allow a country that the global policy blocks, an exception of type allow; if you block one that the global policy does not block, a deny rule of your own is created.
π§ GeoIP does not open ports
GeoIP filters by country at the perimeter layer, but it does not touch ports. If the port or protocol is still closed in your Inbound/Outbound rules, traffic will not get through even if you allow that country.
Before you begin
Log in to the Plenit dashboard.
Have administrative permissions on Servers.
That the network you are going to work on has at least one public IP.
Step 1. Access GeoIP
In the dashboard, open Services β Servers.
In the side menu, go to Firewall.
Open the Geolocation.
{/* πΈ SCREENSHOT 1 Β· Firewall menu with the Geolocation tab */}

Step 2. Select the network
At the top, use the Network selector to choose where to apply GeoIP. You will see the list of public IPs and how many countries each one has blocked.
π 145 countries blocked by default
It's common to see 145 countries blocked from the start. That number may include regions within a country, so it does not always represent the entire country as a single filtering unit.
{/* πΈ SCREENSHOT 2 Β· Network selector and list of public IPs with their country count */}

Step 3. Review the public IPs and enter edit mode
In the table you can see each public IP, its number of blocked countries, and the Edit. Click Edit on the IP you want to adjust.
{/* πΈ SCREENSHOT 3 Β· public IP table with the Edit action */}

Step 4. Manage the countries
Use the continents and countries selector. Checked = blocked; unchecked = allowed (except for global blocking). You have Save, Restore configuration and Cancel.
{/* πΈ SCREENSHOT 4 Β· country selector by continent */}

Step 5. Confirm and apply
Click Save, review the summary and click Confirm. The changes are synchronized with the infrastructure: it is not immediate, it takes a few minutes.
{/* πΈ SCREENSHOT 5 Β· changes summary and Confirm button */}

Step 6. Verify the result
Check the counter of blocked countries blocked countries on the edited IP and run access tests if needed. For a quick check from an origin in the country you want to validate:
Since filtering depends on the country of origin, to test a blocked country you need to connect from that country (for example, through a VPN in that region). If you need to start from scratch, use Restore configuration.
Practical cases
Allow only Spain and Portugal
Check all countries, uncheck Spain and Portugal, Save β Confirm
Temporarily allow Canada
Uncheck Canada, Save β Confirm; when you're done, check it again
You don't know the current state
Restore configuration and start clean from the global policy
Usage tips
Less is more: block first and open only what is essential.
Standardize: apply the same base policy to several IPs and document the exceptions.
Use Restore as a reset when you don't know which rules are applied.
Remember the network layer: if the port or protocol is closed in Inbound/Outbound, traffic will not get in even if you allow the country.
If something doesn't fit
The Confirm button is disabled
There are no changes to apply
Make some changes or exit with Cancel
I allowed a country but it still doesn't work
Propagation is missing or the port is closed
Wait a few minutes and check your Inbound/Outbound rules
I blocked too much and lost access
Policy too restrictive
Use Restore configuration
I don't see the Geolocation tab
The view is not available in your dashboard
Contact Partner Success so they can enable it
Conclusion
GeoIP gives you a simple security lever: you decide by country who reaches your public IPs, without keeping address lists by hand and with a reset button when you need it.
The golden rule is to remember that it acts only on the country of origin: you still govern ports and protocols with the Inbound/Outbound rules, so GeoIP adds to that layer, it does not replace it.
Last updated
Was this helpful?

