A client is not let to access the shop using IPv6 - 503 can't access this store from your country

[StrangeAttractor]

A client has reported he can't access the shop of mine - "Error 503 - Overloaded - You can not access this store from your country" is displayed instead. Maintenace mode is off, the shop works Ok when accessed from IPv4 addresses. The fact the PrestaShop-generated error page with ourlogo is displayed suggests that the hosting provider supports IPv6 and thre client gets connected to the shop but the shop rejects him itself. Any idea about how to fix this?

[tomerg3]

Are you sure you did not restrict his country?

I don't believe PrestaShop has anything to do with IP type.

[El Patron]

When Geo Location is enabled in back office...

 

then non-resolved IP address regardless if ipv4 or 6 will not be allowed to shop.

 

geolitecity data you use is 85% accurate.

 

Strong advice: do not use geo location, simply restrict visitors by 'registration country' and 'shipping'.  but if you price products by country then you will need geo location enabled and Our geo targeting pro module extension which allows you to set default country for non resolved ips, and other features as well.

[StrangeAttractor]

 

 

then non-resolved IP address regardless if ipv4 or 6 will not be allowed to shop

 

Can this be altered?

 

 

 

Strong advice: do not use geo location, simply restrict visitors...

 

I don't want to restrict anybody at all actually, the only reason why I enable geolocation is for the language be chosen automatically (I have translated the shop to more than one language and plan to translate to even more).

 

 

 

Are you sure you did not restrict his country?

 

Regarding the address in this particular case - I don't know to which country does it belong to (as I don't know how does this geolocation stuff work with IPv6 at all) but I am sure the client actually is inside my country physically (moreower, it is not an ordinary Internet user but an employee of the company running the country's most popular search engine trying to reach my site from their office).

Edited December 11, 2014 by StrangeAttractor (see edit history)

[zod]

On 12/11/2014 at 11:06 AM, StrangeAttractor said:

 

Can this be altered?

 

I don't know why no one solved this in the forum. The geolocation is not accurate enough, we should be able to keep the settings for the "maybe" country of the customer, this is useful for the language, currency, and special prices based on country also. But it is very stupid to block "all non resolved IPs", this should be a choice, and mine is not at all.
In fact i had a shop that was blocking some german person for no reason.  To solve this problem we need to override the FrontController. We can modify geolocationManagement or isInWhitelistForGeolocation. The first has some controllers to delete, but the latter is easier, we just need to clean all the code and return true, so any IP is like Whitelisted. This way all "blocking" options that we find under "Geolocation" are bypassed.

So... make this override/classes/controller/FrontController.php

And put this inside...

<?php
class FrontController extends FrontControllerCore
{
    protected static function isInWhitelistForGeolocation()
    {
        return true;
    }
}

 

 

[El Patron]

do not use native geo location, when the ip cannot be resolved it will disallow shopping

see addons for geo targeting pro module, it allows non resolved to used default shop country and supports high resoluiton maxmind database.

https://addons.prestashop.com/en/international-localization/27368-geo-targeting-pro-by-country-prices-taxes-currency-.html

geo is not about guessing, using the free maxmind, is guessing

[zod]

3 hours ago, El Patron said:

do not use native geo location, when the ip cannot be resolved it will disallow shopping

see addons for geo targeting pro module, it allows non resolved to used default shop country and supports high resoluiton maxmind database.

https://addons.prestashop.com/en/international-localization/27368-geo-targeting-pro-by-country-prices-taxes-currency-.html

geo is not about guessing, using the free maxmind, is guessing

In my case the shop is an old PS 1.6, and we want Geolocation just for starting point, to set language and country, to show some special product prices. If it fails it is no harm, it goes default. After all, when the customer is registered, it is his own address that rules the country. So, the geolocation can be the free database version, even if not accurate 100%, it is just a commodity.
The real problem is that we don't want the original behaviour that Prestashop intended, we don't want it as filter that blocks anyone. We never use Prestashop configuration about countries, we want be online for everyone. So my bypass in the isInWhitelistForGeolocation method is good enough for my purpose, anyone is whitelist . Bye

[El Patron]

On 8/20/2020 at 2:56 PM, zod said:

In my case the shop is an old PS 1.6, and we want Geolocation just for starting point, to set language and country, to show some special product prices. If it fails it is no harm, it goes default. After all, when the customer is registered, it is his own address that rules the country. So, the geolocation can be the free database version, even if not accurate 100%, it is just a commodity.
The real problem is that we don't want the original behaviour that Prestashop intended, we don't want it as filter that blocks anyone. We never use Prestashop configuration about countries, we want be online for everyone. So my bypass in the isInWhitelistForGeolocation method is good enough for my purpose, anyone is whitelist . Bye

well you might think that is how it happens...and it will be ok...but I respectfully disagree...geo is not about guessing...good luck