• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx

  • We are developing a new feature in Plesk that will help you promote your websites or business on social media. We want to conduct a one-hour online UX test to present the prototype and collect feedback. If you are interested in the feature, please book a meeting via this link.
    Thank you in advance!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Cloned site redirect wp-admin to main site

nikketrikke

Basic Pleskian
Server operating system version
ubuntu 20
Plesk version and microupdate number
latest
wp-config has the correct db and user
on db home and siteurl point to staging site correctly

i'm using
apache server+proxy nginx + fpm by nginx

but when I open the wp-login point correctly to staging
BUT enter in wp-admin of main site
 
Important i'm using Cloudflare
i point the subdomain in CF to the server ip address...
the stange thing is tht
now i cleared all staging files domain and databse so plesk seems clean
but if i write stage.example.com or staging.example.com already becomes the main live site
seems that cloudflare redirect to the main live site possible?
or that plesk installation is unable to manage subdomains....
 
Hi yes there is
Wprocket
Redis
Nginx server cache
Cloudfoare cache

So i will try to deactivate all and build againnthe close and let you know
 
hi PETER I do this:
cleared all the cache
deactivated
wp rocket
nginx cache
redis cache
nginx helper plugin

allinone security firewall
gtranslate plugin

bypassed and cleared also cloudflare cache

clean the htaccess before cloning leaving only basic options (even if with nginx proxy i suppose not use htaccess)

installed the ssl certificate on staging

NOW SEEMS WORK the admin staging page Wroks...

so i will try to reactivate one by one on live site all the options deactivated to see if something could BREAKS the staging rediects...
thanks for NOW
 
Note that if you use Redis on a WP site that you like to clone, you'll have to manually change the Cache Key (salt). Else the cloned site will use the same Redis catch objects as the source site. Which will cause the behavior you're describing.
 
Back
Top