Support

> with same domaine name (DNS modification not made for now).

This combination is antithetical to the site working. Restoring with the same domain name as the original site means that no change is made to the links. However, if you have not modified the DNS then the domain name to your site does not resolve to the new host (where you restored your site), therefore the links won't work as they are absolute, with the domain name which does not resolve yet.

There is something you are not explaining the right way. If you have not set up the DNS to point to the new server AND you are not using a hosts file for local DNS resolution to the new server's IP address you cannot type in the site's domain name and magically have it served from the new server. It's a fundamental concept of how the Internet (and any TCP/IP network, really) works.

Let's backtrack a bit.

What I understand you are asking me is why you cannot access the new site using the exact same subdomain and domain name as the old site on the new server if you don't use the hosts file on your local computer. The answer to that is what I already said, it's how Domain Name Service (DNS) works since its inception in the 1970s.

If you meant something different, please do clarify so I can help you better.

Okay, I had trouble understanding what you were saying.

Your problem is that you either do not have a .htaccess file OR your host does not support .htaccess files. This is required for permalinks like the ones you have on your site to work.

When you restore a site and go through the entire restoration process the .htaccess is restored as well. If you did not go through the entire restoration it will be left as htaccess.bak, rename it to .htaccess for your site to work.

If you do have a .htaccess file then your host does not allow using .htaccess files or does not support URL redirections. Please contact your host in this case.

Important! All files whose name starts with a dot, like .htaccess, are hidden on most server operating systems. You will need to have your FTP/SFTP client or hosting control panel file manager display hidden files to see if it does exist.

It is an extremely uncommon occurrence. It usually happens on servers where the FTP user and the user the web server runs under are different and these are extremely rare the past decade. This may lead to a situation where the .htaccess file cannot be replaced during the archive extraction phase and also impossible to update during the site restoration phase. Having you manually remove the file and regenerate it works around this problem.