Migrating from Plesk to Bitnami Wordpress Lightsail - Issue 301 Moved Permanently

Keywords: WordPress - AWS - Technical issue - Other

bndiagnostic ID: 0d64af9d-e788-a7ae-9b42-2b9856db1e54

bndiagnostic output:

? Apache: Found possible issues
? Wordpress: Found possible issues
? Resources: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-errors-apache/

bndiagnostic failure reason: I do not know how to perform the changes explained in the documentation

Description:
Hi Bitnami Team,

i migrated from plesk to bitnami wordpress hosted in lightsail AWS.
when migrated, i also using bncert-tools to generate my ssl configuration. After that, i’m trying to access the server the web cannot accessed and when check route direciton found multiple redirection with error 301 moved permanently

next, i using bncert diagnostic for tracing issue and got this major error
AH01630: client denied by server configuration: /opt/bitnami/wordpress
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught TypeError: ftp_fget(): Argument #1 ($ftp) must be of type resource, null given in /opt/bitnami/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php:146Stack trace:#0 /opt/bitnami/wordpress/wp-admin/includes/class-wp-filesystem-ftpext.php(146): ftp_fget()

i can’t found relate documentation to solved this issue
this is diagnostic ticket number 0d64af9d-e788-a7ae-9b42-2b9856db1e54

The redirection issue is clear

❯ curl -LI talentpedia.ayobelajar.id
HTTP/1.1 302 Found
Date: Mon, 20 Jun 2022 07:46:21 GMT
Server: Apache
Location: https://talentpedia.ayobelajar.id/
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 301 Moved Permanently
Date: Mon, 20 Jun 2022 07:46:23 GMT
Server: Apache
Location: https://www.talentpedia.ayobelajar.id/
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 301 Moved Permanently
Date: Mon, 20 Jun 2022 07:46:24 GMT
Server: Apache
X-Redirect-By: WordPress
Location: https://talentpedia.ayobelajar.id/
Content-Type: text/html; charset=UTF-8

Apache redirects to the www domain but WordPress is configured to use the non-www one. You can either update WordPress to use the www domain or remove the www redirection in the WordPress files inside the /opt/bitnami/apache2/conf/vhosts folder.

That’s a WordPress-related question. You will need to ask its support team to get more information.