Title: Geolocation plugin conflict
Last modified: June 27, 2021

---

# Geolocation plugin conflict

 *  Resolved [artisanseo](https://wordpress.org/support/users/artisanseo/)
 * (@artisanseo)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/geolocation-plugin-conflict/)
 * hi,
 * after some experimentation I discovered the cause of a problem I was having when
   using a plugin called “WP Conversion Boost PPCKit” and the geolocation service
   provided by ipinfodb.com
 * a problem that I’d never encountered before –
    Not logged in, the geolocation
   returned Ann Arbor (Michigan) – Incorrect! Logged in, the geolocation returned
   returned my current location – Correct!
 * it was only after I realized that one of the hosting company’s servers (A2 Hosting)
   was located in Ann Arbor that the ‘lightbulb’ went off over my head…
    Caching!
 * turned off LiteSpeed Cache and all was well but as I’d rather keep using it, 
   I’ve got to ask –
    has anything changed in the plugin? are there any backend 
   settings* that address this particular situation? i.e.- the situation being that
   geolocation only works when one is logged into the site
 * * would prefer to avoid messing with htaccess if at all possible
 * thanks

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [artisanseo](https://wordpress.org/support/users/artisanseo/)
 * (@artisanseo)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/geolocation-plugin-conflict/#post-14600599)
 * UPDATE:
    After turning the LiteSpeed Cache plugin onn/off a few times the geolocation
   is (for now?) correct.
 * Now the question is –
    was it this plugin or caching in general? why did happen?
   why did it start? **can I exclude the one page it happened on from being cached?**
 * The ‘Truth’ is out there…
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/geolocation-plugin-conflict/#post-14625367)
 * Hi,
 * when you use LiteSpeed Cache with GeoLocation , you will need to follow this 
   [guide](https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache:geoip-support)
 * to tell server that you want to serve differently over different country
 * otherwise it will just save whoever-comes-first
 * like US user visited first, then it generates US page and serve for all , if 
   UK user visited first, then it generates UK page and serve for all …etc
 * Best regards,
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/geolocation-plugin-conflict/#post-14649153)
 * Hi,
 * I’m going to mark this topic “Resolved”, due to lack of activity.
 * If you still need help, please feel free to re-open it.
 * When re-open it, please also change the topic status to “not solved”
 * Best regards,

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Geolocation plugin conflict’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

## Tags

 * [caching](https://wordpress.org/support/topic-tag/caching/)

 * 3 replies
 * 2 participants
 * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * Last activity: [4 years, 9 months ago](https://wordpress.org/support/topic/geolocation-plugin-conflict/#post-14649153)
 * Status: resolved