Contact person: AWS Devops through Anydesk

Phone:Show

Email:Show

Location: Beograd, Serbia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I have a WordPress production site already running on its own AWS instance. I cloned that instance to spin up a staging server, but whenever I try to log in to wp-admin on staging, I’m immediately redirected back to the live production domain. That is the behaviour I need fixed.

Because I’m not entirely sure where the staging URLs are set inside the database or wp-config, I need someone who can quickly trace and correct every reference that still points to the production domain—typically in wp_options (siteurl / home) and anywhere hard-coded in the database or theme files. Once those values are cleaned up, I expect the staging login page to stay on its own sub-domain / IP and work independently.

Important working notes
• Access: You’ll connect through AnyDesk only. I can’t share direct AWS credentials.
• Environment: Standard LAMP stack on Amazon Linux, Bitnami-style file structure.
• Preferred tools: wp-cli search-replace, phpMyAdmin, or whichever method you trust.
• Secondary concern: if the redirect fix uncovers broader corruption, I may ask you to fall back on an All-in-One Migration export/import workflow. Be aware that the plugin currently throws an “out of disk space” error, so you may have to investigate temp directory size limits or split the archive.

Acceptance criteria
– Staging wp-admin loads and logs in without redirecting to production.
– Front-end URLs on staging no longer jump to the live domain.
– A brief note of exactly what was changed so I can replicate the steps next time.

If you can tackle this through AnyDesk in a single session, please place your bid." (client-provided description)