renamed domain inaccessible

[pskinect]

I changed my domain name and now cannot access my Wordpress site.

When I enter my new domain:

peterschlemowitz.x10host.com/wp

There is an immediate redirect to the old domain:

https://pskinectic.x10host.com/wp/

Which is no longer is available.

The Wordpress install directory has been correctly renamed to peterschlemowitz.xhost.com

Updated SSL certificate which now points to peterschlemowitz.x10host.com

Ping peterschlemowitz.x10host.com works.

 

[Anna]

That is actually a problem with WordPress, the way it is setup it will always try to redirect to the configured domain (usually the one you installed it under) regardless of domain used to reach the site.

This can be changed a few ways, see: https://wordpress.org/support/article/changing-the-site-url/

The simplest solution may be to set the old domain as a pointer domain, this way the redirect would lead to a working domain, and then just login and change the site url settinsg from inside wordpress.

 

[pskinect]

That is actually a problem with WordPress, the way it is setup it will always try to redirect to the configured domain (usually the one you installed it under) regardless of domain used to reach the site.

This can be changed a few ways, see: https://wordpress.org/support/article/changing-the-site-url/

The simplest solution may be to set the old domain as a pointer domain, this way the redirect would lead to a working domain, and then just login and change the site url settinsg from inside wordpress.

The current install of Wordpress was made after the domain was changed as the old one was deleted. I have reconfigured the site and home url both in the Wordpress admin page and in the post_options table to no avail. I added the domain pointer but now I get a Your connection is not private error as the certificates points to the new target domain. The question is how does the domain get switched to the old domain in the first place? I have looked through all the Wordpress tables and there is no reference to pskinectic nor is there any in the files that provide links to the homepage.

After continuing the link ignoring the error the DNS pointer error seems to have disappeared but still get private error. No longer can used the request SSL option so have installed from self generated, that may be the problem.

Looks like the problem is that the Chrome cached the reference.

 

[Anna]

Your site loads up fine for me, using the new domain.

Self generated SSL is generally not regarded as safe by browsers, as the certificate isn't provided by a known authority and thus not trusted by the browser.