# Wrong location in linux (cont 2)

**URL:** <https://community.brave.app/t/wrong-location-in-linux-cont-2/508774>\
**Category:** Desktop Support\
**Tags:** linux\
**Created:** [October 4, 2023, 11:49pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774 "2023-10-04T23:49:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 4, 2023, 11:49pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/1 "2023-10-04T23:49:50Z")

</div>

Continuing the discussion from [Wrong location in linux](https://community.brave.app/t/wrong-location-in-linux/466188/2):

**Description of the issue:**  
Brave shows wrong location in Linux desktop.

**How can this issue be reproduced?**

1. Open [google.com/maps](http://google.com/maps)
2. Click on the show current location button (blue one over zoom buttons)
3. It shows a location far from mine

**Expected result:**  
Show current location

**Brave Version( check `About Brave`):**  
[  
Versión 1.58.137 Chromium: 117.0.5938.153 (Build oficial) (64 bits)  
 ](https://brave.com/latest/)

**Additional Information:**

- Not on VPN
- Allowed access to location for [google.com](http://google.com/)
- Already tried removing cookies and cache data, and it didn’t fix it
- It works on Google Chrome and Firefox browsers and in Gnome Maps application, so not an ISP problem
- The same occurs in a private window.

I’ve seen lots of posts about this, in one someone said clearing the cache solved for him, but it didn’t do a thing in my case, all of those seem to be dismissed. And I can comment on them.

This problem has been present since I started using brave, I’ve seen lots of similar posts, always the same suggestions from the staf and it never helps. It seems to be a bug in brave, otherwise please tell me what was I doing wrong, considering that I already tried all variants suggested, and all of that is in this description

Update: it happens the same in the snap version, without any customization, and the location detected is the same as the deb distributed version.

---

<div class="post-metadata">

**Author:** ![JimB1](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@JimB1](https://community.brave.app/u/JimB1)\
**Post date:** [October 5, 2023, 1:02am UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/2 "2023-10-05T01:02:53Z")

</div>

I still think there are good odds it is DNS related, it may be challenging to demonstrate but we can give it a shot.

If you go to [https://dnsleaktest.com/](https://dnsleaktest.com/) and run the ‘extended test’ in each browser, say Brave vs. Firefox, do you get different results?

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 5, 2023, 1:17am UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/3 "2023-10-05T01:17:27Z")

</div>

In google chrome, where location roks ok:

 ![image](https://global.discourse-cdn.com/brave/original/3X/2/3/2372a5bcdb966aaca55ef0e0b32a2e15ca7adcbc.png)

In brave where it doesn’t:

 ![image](https://global.discourse-cdn.com/brave/original/3X/9/b/9bf1f149c088d40758fcb668a3282fcb7a27f944.png)

In firefox, where location works:

 ![image](https://global.discourse-cdn.com/brave/original/3X/0/5/05b4b839d94272072ba2927b4e5d883cbd571288.png)

En epiphany, where location also works:

 ![image](https://global.discourse-cdn.com/brave/original/3X/e/9/e908bccb5eea52272e8f4e101e566d37943a58a6.png)

Not sure what is a DNS leak, but the only browser where location does not work for me is brave.

---

<div class="post-metadata">

**Author:** ![JimB1](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@JimB1](https://community.brave.app/u/JimB1)\
**Post date:** [October 5, 2023, 1:54am UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/4 "2023-10-05T01:54:28Z")

</div>

> [@alcarraz](#):
>
> Not sure what is a DNS leak, but the only browser where location does not work for me is brave.

Yup, got it, you explained that already. But the point here isn’t any ‘DNS leak’ itself, but to see if we can ferret out a difference in the way your DNS lookups are being performed. As I said, it’s going to be challenging unless you are able to review everything relevant directly on your end.

The way DNS-based geolocation normally works is an authoritative name server determines your location based on a client subnet as perceived by your DNS resolver, for example Google Public DNS. And it can then change the web servers you target based on that; this doesn’t necessarily translate into the web site serving you different content (i.e. a different map location in this case), but a different DNS resolver result would be an indirect means of showing that in Browser X you are seen as coming from a certain IP, whereas in Browser Y it’s a different IP.

Another thing we can look at is: [https://whatismyipaddress.com/](https://whatismyipaddress.com/)

You don’t have to tell us the exact IP result, but, is it the same across the browsers?

And, does it give the same geolocation problem as Google Maps?

Also providing a screenshot of `brave://settings/security` may help.

---

<div class="post-metadata">

**Author:** ![Saoiray](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/saoiray/32/212354_2.png) [@Saoiray](https://community.brave.app/u/Saoiray)\
**Post date:** [October 5, 2023, 2:03am UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/5 "2023-10-05T02:03:22Z")

</div>

@alcarraz just wanted to butt in to kind of ask a few things.

1. Are you actually still on 1.47.186? If so, can you try updating and see if anything changes?

2. Does turning off Shields change anything?

3. Do you have Google or Google Maps under `Not allowed to see your location` at `brave://settings/content/location`?

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 5, 2023, 11:42pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/6 "2023-10-05T23:42:00Z")

</div>

Sorry I didn’t update the version,

1. I’m always in the latest available for Ubuntu, currently 1.58.137 and the problem persists.
2. I already tried that (one of the first things) and didn’t fix it. In fact I have it disabled right now for maps.
3. No, I don’t have it there, in fact it is in the list of the sites that have access.

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 5, 2023, 11:46pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/7 "2023-10-05T23:46:32Z")

</div>

> [@JimB1](#):
>
> brave://settings/security

 ![image](https://global.discourse-cdn.com/brave/original/3X/c/c/cc3a324a2377c7444d2395a4af97fab247fd4e1c.png)

The what’s my IP site shows the same IP in all browsers.

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 10, 2023, 7:18pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/8 "2023-10-10T19:18:49Z")

</div>

Hi @Saoiray, anything else you think it could help solve this problem?, judging for the other ones posting the same issue, it does not only happen in linux, but also in windows. None of the topics I found had a satisfying closure. All of them were closed by timeout.

Happy birthday by the way 🎂

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 10, 2023, 7:22pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/9 "2023-10-10T19:22:00Z")

</div>

Thank you, @JimB1 What steps should I perform to check what brave is doing differently than all other software in my machine?

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 10, 2023, 7:29pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/10 "2023-10-10T19:29:31Z")

</div>

Update, I tried the snap version, without any customization, and resolves to the same location as the deb version.

---

<div class="post-metadata">

**Author:** ![alcarraz](https://sea1.discourse-cdn.com/brave/user_avatar/community.brave.app/alcarraz/32/155290_2.png) [@alcarraz](https://community.brave.app/u/alcarraz)\
**Post date:** [October 17, 2023, 9:47pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/11 "2023-10-17T21:47:52Z")

</div>

Bump, so it doesn’t get closed

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/brave/original/3X/1/8/182067f3480d1a5e7aea5ae3131b116ca1ef7918.png) [@system](https://community.brave.app/u/system)\
**Post date:** [November 16, 2023, 9:48pm UTC](https://community.brave.app/t/wrong-location-in-linux-cont-2/508774/12 "2023-11-16T21:48:22Z")

</div>

Closed on November 16, 2023, 9:48pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
