So, you have gone through all this work to find a domain, transfer it or something rather to 1&1 (or another service). You have everything pointing to the right place in the interface and then when you go to the domain in your browser it is pointing to the 1&1 /defaultsite. What is the deal!
Well after pulling my hair our and doing some digging, I came across this thread on 1and1 redirecting to defaultsite: https://productforums.google.com/forum/#!topic/apps/v9YNjxKRuKc. While this thread gets at the issue, it doesn’t explain how to resolve it super explicitly, so here is the basic solution: if you are using Chrome browser, reset your proxy settings for you wifi. If you try to access via Safari, your site should work normally without resetting anything.
So if you don’t know how to reset your proxy settings on Chrome, here is how to do it. First go to the “three dot” dropdown and select “Settings”.
Next, a tab will open to the settings page. Go to Network and click “Change Default Settings” button. You may have to click the “Show Advanced Settings” button to get to this.
Once you have clicked “Change Default Settings”, if you are on a Mac, you will see the below popup from your computer settings. Select the proxy you would like to use. I choose “Auto Proxy Discovery” but you may want to pick something else with additional research.
Should be off to the races after that!
Also checkout this 1&1 article about how to access .htaccess file within 1&1.
Thanks, but can anyone explain “why” this is necessary?
And more importantly, why even after doing this if you explicitly go to yoursite.com/defaultsite, you still get 1and1’s crappy spam page?
I have not been able to find a way to disable the /defaultsite page.
if youre seeing 1and1’s page instead of your own then either you’re seeing a cached page, or your domain’s DNS records aren’t set properly, or if they are they haven’t fully propagated around the internet which can take anywhere from one to 48 hours
Dude, thank you. I was losing my mind!
Glad I could help!
Yes thanks so much. I never knew cashed files on the client side could affect delivery from the server side.
Hi ! please i’m running on Linux and i have the same problem but i can’t solve it the same way
Any idea ?
This just happened to me, too . I’m not on a Mac so the settings for Chrome in a PC don’t look like the images above. However, the way we fixed it, oddly enough, was to reset my router. Apparently, there’s a cache stored in the router. I asked 1and1 why I could see the site in MS Edge but not in Chrome and he told me it’s not necessarily a Chrome issue. It tends to happen to whatever browser you use most often.
Is there a way to fix this issue on an Android phone? I have this issue on my phone but not desktop.
or you can press ctrl+shift+delete (in chrome) and clear your cache. This did it for me.
legend !! I was very stressed with this 🙂 happy happy thanks thanks
ctrl+shift+delete and select to delete cache also works for firefox!
thanks dude!
Thanks bro. I was going crazy. It was working on my mobile browser but not on Chrome through my computer. Tried many solutions but only this one helped. Thanks again
Your welcome!
Sometimes there is an issue with SSL aswell. If you have moved your site to another domain which had SSL and you cloned the website. You have to make sure the new site has an SSL certificate installed through your host or another provider, and also you need to make sure you have changed the options through phpMyadmin and logged into your database and changed the wp-options area.
Thanks for the additional information!
For me 1and1 had set AAAA records pointing to their hosting service which I don’t use.
Trying to edit this and clear it out was impossible as the IPv6 box was empty. Despite that box being empty, their AAAA record persisted.
What worked was changing it over to a CNAME. This cleared out both the A and AAAA records. Then I changed it back to A record.
Clearing cached images and files in Chrome on MacOS 10.14.4 fixed it for me. Go to Settings and search for “cache”.
The question is: if I cant see my website because of some google chrome shit, other people with chrome will be also unable to see my website? then they will just give up and leave my site, because they wont try to solve this problem to see a random website.
Hi All,
I’ve read alot about how to combat the IONOS issue of the redirect to defaultsite and seen many examples of how people are combatting the issue. Many of the responses on how to combat it would require the end user to change their seetings too. This is not a solution, if only you can view it after implementing changes. Anyway, I wanted to share an answer that will resolve the problem with ease. If you are being redirected as an example to https://example.com/defaultsite, you can fix it in your route file like so:
Route::get(‘/defaultsite’, function () {
return redirect(‘/’);
});
This simply redirects the webpage from ‘defaultsite’ to your web route ‘/’ where your public index should be located.
I hope this helps!
This is very helpful Garry. Thanks for sharing the solution.
Just change the forwarded URL from (eg.) Your.domain.com to Your.domain.com/#
The # will cause anything after the URL (/defaultsite) to be ignored.
Thanks for the additional way to solve this!
For me the problem was a cached 301 forward in Firefox. You can see it in the Debugger networking tab. It doesn’t go away by restarting or hitting Ctrl+F5.
I solved it by opening the history sidebar, rightclicking any of my websites entries and choosing “forget about this site”.
Thank you so much 🙂