Upgrading instance breaks wp-config

Keywords: WordPress - AWS - Technical issue - Upgrade
Description:
Hi All,

I’m running the Bitnami Wordpress Aurora stack. https://aws.amazon.com/marketplace/pp/Bitnami-WordPress-with-Amazon-Aurora-Certified-by-/B075JZRRG5

I followed the guide (https://docs.bitnami.com/aws/faq/administration/change-server-type/) to upgrade my EC2 instance to a faster server, but once rebooted I was presented with the stock wp config setup screen instead of my configured Wordpress website. When I downgraded back to the original server instance, it was working again but with a new url and ip. Is there a way to upgrade the instance and not have to reconfigure wordpress config file?

Kind regards

David

Hi @DWH,

I launched one of the following templates and upgrade the instance to a bigger size but couldn’t reproduce your issue. Do you remember which one of the proposed templates did you launch?

This is normal. The public IPs are dynamics so they will change if you restart your server.
Normally, you would buy a static IP for your server and a domain name pointing to that static IP so you can always reach your WordPress at https://your_domain.com.

Hi @tomasp,

Thanks for taking a look. The fulfilment option was ‘Wordpress with aurora by bitnami and automatic’. I don’t mind so much about the new ip, I was just hoping for an easy way to boost the machine size when it moves from dev into production. Any ideas why the wp sample config would appear after upgrading the machine instance, but then disappear once you downgrade?

Kind regards

David

Hi @DWH,

I tried again with that template to be sure I didn’t try with the other in my first attempt. The result has been the same, I was able to upgrade to a bigger instance and downgrade later without any issues.

Would be possible for you to give another try?

Will do, thanks. @tomasp

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.