-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WordPress Multisite] RDS database - connection issues #978
Comments
If you get that error message, please review the database's configuration in the wp-config.php file.
You can just launch a new instance and migrate the data https://docs.bitnami.com/general/how-to/migrate-wordpress/ You can also move to the Bitnami WordPress Chart solution that solves that problem. You can easily upgrade the solution without the need of launching a new server and migrating the data. https://docs.bitnami.com/aws/get-started-charts-eks-marketplace/ |
Hi, "If you get that error message, please review the database's configuration in the wp-config.php file." As I said in the issue I can connect from the command line when SSH'd into the Bitnami instance to the database using the same details in the wp-config.php file, so the issue is not there. I have looked at the link you sent but can't see anything that applies. |
Decided to try the other suggested solution: "You can also move to the Bitnami WordPress Chart solution that solves that problem. You can easily upgrade the solution without the need of launching a new server and migrating the data. https://docs.bitnami.com/aws/get-started-charts-eks-marketplace/" Followed all the instructions, got to the end of step 5 in the prerequisites https://docs.bitnami.com/aws/get-started-eks/, prompted for username when I shouldn't be (or at least no mention of it, so now trawling around the internet trying to find a fix for that |
Hi, I just took a quick look at the cluster creation form in AWS and it didn't ask for a username. You can contact the AWS support team if you have any issues during the cluster creation. Apart from that, you can use the eksctl CLI tool to create the cluster As an alternative, I also suggest you use minikube or any similar alternative to deploy the solution locally and confirm that it meets your needs. |
It is not a problem creating the cluster, it has been created and is active: https://capture.dropbox.com/CCfTibKYLu9meBgA It is running the command below to verify the creation (the end of Step 5): I get prompted for a username and a password, so I enter something random (as I never created a username or password as part of the instructions). I get this error: https://capture.dropbox.com/Aep0IN6T3LZeWhMu No idea where to go from there, And what about the db connection for the original issues, any suggestions on that? So far neither solution is any good for me and I'm stuck with a product I can't upgrade to a supported version. |
Do not know why you are being asked for a username/password when running the command. Will need to review the guide to know if we need to update it.
You can try to connect to the database with a custom PHP script and confirm that the credentials are valid https://www.w3schools.com/php/php_mysql_connect.asp If you continue running into issues with WordPress and the db connection, I suggest you contact them to know more about the issue and how to troubleshoot it. |
Your guides are out of date. I managed to get past the original issue of being prompted for a username, but then could not run kubectl as the due to permissions issues. These were resolved by creating the cluster via the cli. However now falling this https://docs.bitnami.com/aws/get-started-charts-eks-marketplace/ on step 2. I get the error "Error: INSTALLATION FAILED: create: failed to create: namespaces "kubeapps" not found". That was after multiple steps in the AWS marketplace being different from the ones in the guide. I just want a working up to date wordpress environment and am getting increasingly frustrated. |
Instead of fighting with the EKS cluster, you can deploy it locally with minikube or the docker solution and test the solution first.
Did you try this? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Platform
AWS
bndiagnostic ID know more about bndiagnostic ID
6fdbac62-c7be-a793-59e5-bfc389d8398f
bndiagnostic output
===== Begin of bndiagnostic tool output =====
[Connectivity]
Server ports 22, 80 and/or 443 are not publicly accessible. Please check the
following guide to open server ports for remote access:
https://docs.bitnami.com/general/faq/administration/use-firewall/
[Wordpress]
Press [Enter] to continue:
Some files don't have the expected permissions Please check the following guide:
https://docs.bitnami.com/general/apps/wordpress/administration/understand-
file-permissions/
[Apache]
Found recent error or warning messages in the Apache error log.
Please check the following guide to troubleshoot server issues:
Press [Enter] to continue:
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro
rs-apache/
===== End of bndiagnostic tool output =====
bndiagnostic was not useful. Could you please tell us why?
The suggested ports are open, so the tool is incorrect. My specific issue is not listed
Describe your issue as much as you can
I am trying to migrate my Wordpress Multisite from an older Bitnami stack to a new one. I have the below set up:
Existing:
EC2 Server
RDS Database (MySql)
Elastic IP
New:
EC2 Server
RDS Database (MariaDB)
I backed up the old site with Wp-Staging, created the new EC2 server with the new Bitnami stack. I then create a new RDS instance, did a SQL dump from the internal MariaDB on the new server, and ran that on the new RDS instance. I changed the wp-config file and verified connection to the database from the command line in the new EC2 instance (I’d already set up the appropriate rules in the Security Groups.
I then changed the Elastic IP (that all the DNS entries point to) to be associated with the new instance. I also changed the below files/db tables to have the appropriate (existing) domain:
wp-config.php
wp_options
wp_site
wp_blogs
When I access the site I get an "Error establishing a database connection" message. I re-confirmed connection to the db from the EC2 instance command line, and it is fine. As is connecting to the db through my local machine.
What else to I need to change?
I am finding the upgrade process for Bitnami to be incredibly frustrating just to get the latest version of PHP and Wordpress I need to build an entire new environment, with little to no user guides (that google can find anyway.)
I’ve reverted back to my old environment in the meantime.
The text was updated successfully, but these errors were encountered: