Google domain in address bar different
up vote
0
down vote
favorite
I live in Canada and use Google.ca exclusively. It's been set as my default search engine for years. For the past couple days, when I enter a search in the Chrome address field, search results return from the United Arab Emirates, like this:
The weird part is if I enter the search in the Google home page search field, the search return under Google.ca.
I checked my Region Settings under Google Home > Settings > Region Settings. They were set to Current Region (I'm in Canada, never been anywhere near the UAE) but I changed the setting to Canada to see if that helped. (The bottom of my Google Home settings were showing Unite Arab Emerates, but now they show Canada after I made the change:
This seemed to fix the search domain for the Google Home page but now the Chrome address field. (Weird they would be different?)
I also checked my language settings in my Google settings and they're English.
I have an ExpressVPN account and it puts my IP in the U.S. (I verified). Also, they issue is on all my devices.
I did set up a couple new Google Homes (Insignia brand) a day before the problem started. I can't imagine its related, but the weird part is they don't seem to recognize my voice as well since this issue started?
Also, I check to see if any weird Chrome extensions were added during a recent install and there were none. I also ran MalwareBytes which found a bunch PUP setting issues
Which I quaranteed, but no improvements.
I'm out of ideas. Thoughts greatly appreciated!
google-chrome search
add a comment |
up vote
0
down vote
favorite
I live in Canada and use Google.ca exclusively. It's been set as my default search engine for years. For the past couple days, when I enter a search in the Chrome address field, search results return from the United Arab Emirates, like this:
The weird part is if I enter the search in the Google home page search field, the search return under Google.ca.
I checked my Region Settings under Google Home > Settings > Region Settings. They were set to Current Region (I'm in Canada, never been anywhere near the UAE) but I changed the setting to Canada to see if that helped. (The bottom of my Google Home settings were showing Unite Arab Emerates, but now they show Canada after I made the change:
This seemed to fix the search domain for the Google Home page but now the Chrome address field. (Weird they would be different?)
I also checked my language settings in my Google settings and they're English.
I have an ExpressVPN account and it puts my IP in the U.S. (I verified). Also, they issue is on all my devices.
I did set up a couple new Google Homes (Insignia brand) a day before the problem started. I can't imagine its related, but the weird part is they don't seem to recognize my voice as well since this issue started?
Also, I check to see if any weird Chrome extensions were added during a recent install and there were none. I also ran MalwareBytes which found a bunch PUP setting issues
Which I quaranteed, but no improvements.
I'm out of ideas. Thoughts greatly appreciated!
google-chrome search
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I live in Canada and use Google.ca exclusively. It's been set as my default search engine for years. For the past couple days, when I enter a search in the Chrome address field, search results return from the United Arab Emirates, like this:
The weird part is if I enter the search in the Google home page search field, the search return under Google.ca.
I checked my Region Settings under Google Home > Settings > Region Settings. They were set to Current Region (I'm in Canada, never been anywhere near the UAE) but I changed the setting to Canada to see if that helped. (The bottom of my Google Home settings were showing Unite Arab Emerates, but now they show Canada after I made the change:
This seemed to fix the search domain for the Google Home page but now the Chrome address field. (Weird they would be different?)
I also checked my language settings in my Google settings and they're English.
I have an ExpressVPN account and it puts my IP in the U.S. (I verified). Also, they issue is on all my devices.
I did set up a couple new Google Homes (Insignia brand) a day before the problem started. I can't imagine its related, but the weird part is they don't seem to recognize my voice as well since this issue started?
Also, I check to see if any weird Chrome extensions were added during a recent install and there were none. I also ran MalwareBytes which found a bunch PUP setting issues
Which I quaranteed, but no improvements.
I'm out of ideas. Thoughts greatly appreciated!
google-chrome search
I live in Canada and use Google.ca exclusively. It's been set as my default search engine for years. For the past couple days, when I enter a search in the Chrome address field, search results return from the United Arab Emirates, like this:
The weird part is if I enter the search in the Google home page search field, the search return under Google.ca.
I checked my Region Settings under Google Home > Settings > Region Settings. They were set to Current Region (I'm in Canada, never been anywhere near the UAE) but I changed the setting to Canada to see if that helped. (The bottom of my Google Home settings were showing Unite Arab Emerates, but now they show Canada after I made the change:
This seemed to fix the search domain for the Google Home page but now the Chrome address field. (Weird they would be different?)
I also checked my language settings in my Google settings and they're English.
I have an ExpressVPN account and it puts my IP in the U.S. (I verified). Also, they issue is on all my devices.
I did set up a couple new Google Homes (Insignia brand) a day before the problem started. I can't imagine its related, but the weird part is they don't seem to recognize my voice as well since this issue started?
Also, I check to see if any weird Chrome extensions were added during a recent install and there were none. I also ran MalwareBytes which found a bunch PUP setting issues
Which I quaranteed, but no improvements.
I'm out of ideas. Thoughts greatly appreciated!
google-chrome search
google-chrome search
asked Nov 30 at 0:27
buttonsrtoys
171110
171110
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09
add a comment |
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379611%2fgoogle-domain-in-address-bar-different%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried a fresh Chrome user profile? Google attempts to use Geolocation. So make sure that this happens when you are NOT connected to your VPN, and it does happen, with other browsers. If it happens only while connected to a VPN and with all browsers, then this is a problem with Google’s Geolocation or your Google account (which then would justify moving this question)
– Ramhound
Nov 30 at 0:50
Thanks @Ramhound. I disconnected the VPN and that fixed the problem. I've had the VPN for a couple months and the issue only started a couple days ago. Do you think it's still related to Google's Geolocation?
– buttonsrtoys
Nov 30 at 12:04
I think it’s due to the VPN true server location, either that, Google has old information with regards to the address itself.
– Ramhound
Nov 30 at 12:51
I reconnected the VPN and the problem returned. Investigating, my D-Link 810L firmware was out of date (1.01). I updated to 1 03 and it fixed the problem.
– buttonsrtoys
Dec 1 at 13:09