Skip to content
Grav 2.0 is officially stable. Read the announcement →

Community guidelines

Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.

Installation & Hosting

Moving to another webspace nd domain

Solved by Olivier View solution

Started by Olivier 5 years ago · 3 replies · 1140 views
5 years ago

Hi,

I'd like to move our installation from a webspace and domain fleegeelteren-lëtzebuerg.lu to another one with domain fel.lu (@ easyname.com)

Problem: After copying all the files to the new webspace and calling the new domain, I always end up at the old one. Previously a parked domain message was shown, but I changed the domain-settings to the webspace-directory. (fyi, changing this to google shows google ;) )

Maybe someone could tell me why it doesn't work? ;)

Thx
Olivier

last edited 05/03/21 by Olivier
5 years ago

... or in other words: is there a file in Grav that specifies the home-adress of the site?

Why entering flek.lu that points to a directory of the webspace ends up at fleegeelteren-lëtzebuerg.lu resp. xn--fl... ? It has to be a simple configuration I guess, I just can't find it.

5 years ago

Hi there @idoki,
I wondering if you are chasing your tail, I tried to check the dns enteries which your two domains control panel would be set up

https://www.whatsmydns.net/#A/fel.lu
gives an ip address of 77.244.243.51 which does take you to an easyname parked domain message.

https://learn.getgrav.org/17/advanced/change-site-url

you can check the system.yaml

but see it forwards to a sub directory of /lb

so you might find there is a redirect to the domain running as well as the fleegeelteren-lëtzebuerg.lu doesnt report a ip address.

Maybe just do a test and install a fresh copy of grav in to a sub directory, lets say grav-test and then see if you can get access to the webspace by using the ip and the subdirectory in the browser by http:\\77.244.243.51\grav-test\

to ensure your host (easyspace) is accessible, is something weird happens, you know it either the system.yaml or a .htaccess or redirect or custom route that has been setup

Just to add, i thought I would ping the address of the working website and got this link https://xn--fleegeelteren-ltzebuerg-2dc.lu/lb notice the prefix xn-- , so some sort of redirect in place
:) which traced to the visible site being on https://kasserver.com/

last edited 05/10/21 by Spam Hater
5 years ago Solution

OK, if you know the reason it's quite simple :

There was an (with my settings for me invisible invisible) htaccess in the webroot-directory with a redirect 😉

So problem solved

Suggested topics

Topic Participants Replies Views Activity
Installation & Hosting · by antoinep, 20 hours ago
7 73 2 hours ago
Installation & Hosting · by Jürgen Dietrich, 7 months ago
0 65 7 months ago
Installation & Hosting · by rappluk, 8 months ago
0 65 8 months ago
Installation & Hosting · by N, 12 months ago
3 76 12 months ago
Installation & Hosting · by Youle, 1 year ago
1 65 1 year ago