Facebook
Twitter
ben-tomsen
New Pleskian
- Server operating system version
- Ubuntu 22.04.4 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.58.2
TLDR: Please help me troubleshoot this. I am struggling with some sort of automatic redirect, but I can't find where that is configured - so I can't get rid of it! I have full access to Plesk and to SSH, but haven't found a way to turn off the redirection.
Details:
I used the WordPress plugin "Duplicator" to clone a WP site from one subdomain to another. In Plesk I had created the destination as a blank space, no WordPress (because the plugin boasts it can install from scratch). That seemed to work but it also caused the source site to be redirected to the new copy -- definitely not what I wanted!
https:// 2024 . foo.bar/ redirects to
https:// 2024c. foo.bar/ and I don't want that.
It then seemed like a cache issue because another browser (Firefox) didn't have the redirect; the source site was OK! So I cleared the cache in Chrome and saw that the redirect was gone again. Weird, but okay!
Using Plesk, I then removed the entire new clone because I want to repeat what I did.
The source site still works, but then I discovered that any URL with
https:// 2024 . foo.bar/ is fine but
https:// 2024 . foo.bar/wp-login.php shows a broken login page that seems to come from
https:// 2024c . foo.bar/ and I don't want that.
Clearing browser caches, or using private browsing mode, does not resolve this.
I have created a new webspace at https:// 2024c . foo.bar/ and now I'm back to:
https:// 2024 . foo.bar/ redirects to
https:// 2024c . foo.bar/ and I don't want that.
Details:
I used the WordPress plugin "Duplicator" to clone a WP site from one subdomain to another. In Plesk I had created the destination as a blank space, no WordPress (because the plugin boasts it can install from scratch). That seemed to work but it also caused the source site to be redirected to the new copy -- definitely not what I wanted!
https:// 2024 . foo.bar/ redirects to
https:// 2024c. foo.bar/ and I don't want that.
It then seemed like a cache issue because another browser (Firefox) didn't have the redirect; the source site was OK! So I cleared the cache in Chrome and saw that the redirect was gone again. Weird, but okay!
Using Plesk, I then removed the entire new clone because I want to repeat what I did.
The source site still works, but then I discovered that any URL with
/wp-admin/... still redirects?! To the site that no longer exists (and it would be the wrong site anyway):https:// 2024 . foo.bar/ is fine but
https:// 2024 . foo.bar/wp-login.php shows a broken login page that seems to come from
https:// 2024c . foo.bar/ and I don't want that.
Clearing browser caches, or using private browsing mode, does not resolve this.
I have created a new webspace at https:// 2024c . foo.bar/ and now I'm back to:
https:// 2024 . foo.bar/ redirects to
https:// 2024c . foo.bar/ and I don't want that.
