301 redirect of a page on Bitnami AWS Lightsail Linux Wordpress site

gotzon 2020-05-17 20:45:01 UTC #1

Keywords: WordPress - AWS - How to - Other
Description:
Hello!
I have checked through the instructions but it in the below articles:

https://docs.bitnami.com/aws/apps/wordpress/administration/redirect-custom-domains/
https://docs.bitnami.com/aws/apps/wordpress/administration/use-htaccess/

But unfortunately I am still unable to set up 301 redirect of a page on my wordpress site. I need www.somehing.com/men/ to forward to www.somehing.com/cat/men/

I tried adding the below line to both htaccess.conf and httpd-app.conf but neither resulted in success.

Redirect 301 "/men/" "/cat/men/"

Thank you

gongomgra 2020-05-18 09:16:24 UTC #2

Hi @gotzon,

Thanks for using Bitnami. We have a Support Tool that will gather relevant information for us to analyze your configuration and logs. Could you please execute it on the machine where the stack is running by following the steps described in the guide below?

Please note that you need to paste the code ID that is shown at the end.

gotzon 2020-05-18 16:55:43 UTC #3

Hello @gongomgra,

Thank you for your reply! I am happy to say that after rebooting the whole server from the console, now redirecting working! I do not know if I had the command at wrong place in the file, but now it is working.

I am having another issue with the htaccess.conf and httpd-app.conf files, and I was wondering if I could ask for your help.

I have offloaded our media to a subdomain media, as suggested in this post.
Offloaded files in media subdomain include .SVG which are not passing CORS rule.
So I have tried adding the below code to both htaccess.conf and httpd-app.conf files, but I am still not passing CORS rule:

 <FilesMatch "\.(ttf|otf|eot|woff|svg)$">
        <IfModule mod_headers.c>
            SetEnvIf Origin "http(s)?://media\.MY_DOMAIN\.com$" AccessControlAllowOrigin=$0
            Header add Access-Control-Allow-Origin %{AccessControlAllowOrigin}e env=AccessControlAllowOrigin
            Header merge Vary Origin
        </IfModule>
    </FilesMatch>

Are you able to advise me please?
The ID is f6924531-6f79-23c8-c13c-73e7171c014f.

Thank you!

gongomgra 2020-05-19 10:29:46 UTC #4

Hi @gotzon,

According to our guide below, you only need to add one line in the /opt/bitnami/apps/wordpress/conf/httpd-app.conf file to activate CORS features in WordPress.

https://docs.bitnami.com/aws/apps/wordpress/configuration/enable-cors-wordpress/

Header set Access-Control-Allow-Origin "*"

Then, you need to modify the /opt/bitnami/apps/wordpress/conf/htaccess.conf file with your custom configuration for the media files. Can you try this setting and then restart services?

sudo /opt/bitnami/ctlscript.sh restart

Please run the bnsupport tool again so we can check your updated config in case you continue getting errors

gotzon 2020-05-19 20:35:11 UTC #5

Hello @gongomgra !
Thank you for your quick reply! I am sorry I had missed your article on CORS when I was searching on the topic.

So, to start, I decided only to apply the first rule in the /opt/bitnami/apps/wordpress/conf/httpd-app.conf file. I thought as it is the most permissive, I should check first I can apply that successfully. So I inserted this:
Header set Access-Control-Allow-Origin "*"
right after line <Directory "/opt/bitnami/apps/wordpress/htdocs">

Yet I am still getting the same CORS error message. No Access-Control-Allow-Origin header is present on the requested resource.

I ran the support tool again, ID is now 2b786570-a86f-37b8-e794-c97712cf9116.

Are you able to help me to troubleshoot what I've done wrong?
Thank you

gongomgra 2020-05-20 09:33:28 UTC #6

Hi @gotzon,

I visited your website using cURL and I see the Access-Control-Allow-Origin header is being properly set as you can see next

curl -vLI "http://www.vanassibara.com"
* Rebuilt URL to: http://www.vanassibara.com/
*   Trying 52.56.78.221...
* Connected to www.vanassibara.com (52.56.78.221) port 80 (#0)
> HEAD / HTTP/1.1
> Host: www.vanassibara.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Wed, 20 May 2020 09:20:20 GMT
Date: Wed, 20 May 2020 09:20:20 GMT
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Connection: keep-alive
Connection: keep-alive
< Set-Cookie: AWSALB=OoYLkWHM/pgFiPzQV8onb6zFGdZPEEPQ1UvdffLD4H/oHn4Jcc2NVW5xQHCsJIAnFIDrDOmF/qVSllGqL5nCKy49XvTu40qPitfwyO3y/TfjuS0D+ff5OL1G06Ip; Expires=Wed, 27 May 2020 09:20:20
GMT; Path=/
Set-Cookie: AWSALB=OoYLkWHM/pgFiPzQV8onb6zFGdZPEEPQ1UvdffLD4H/oHn4Jcc2NVW5xQHCsJIAnFIDrDOmF/qVSllGqL5nCKy49XvTu40qPitfwyO3y/TfjuS0D+ff5OL1G06Ip; Expires=Wed, 27 May 2020 09:20:20 GM
T; Path=/
< Set-Cookie: AWSALBCORS=OoYLkWHM/pgFiPzQV8onb6zFGdZPEEPQ1UvdffLD4H/oHn4Jcc2NVW5xQHCsJIAnFIDrDOmF/qVSllGqL5nCKy49XvTu40qPitfwyO3y/TfjuS0D+ff5OL1G06Ip; Expires=Wed, 27 May 2020 09:20
:20 GMT; Path=/; SameSite=None
Set-Cookie: AWSALBCORS=OoYLkWHM/pgFiPzQV8onb6zFGdZPEEPQ1UvdffLD4H/oHn4Jcc2NVW5xQHCsJIAnFIDrDOmF/qVSllGqL5nCKy49XvTu40qPitfwyO3y/TfjuS0D+ff5OL1G06Ip; Expires=Wed, 27 May 2020 09:20:2
0 GMT; Path=/; SameSite=None
< Server: Apache
Server: Apache
< X-Powered-By: PHP/7.3.14
X-Powered-By: PHP/7.3.14
< X-Redirect-By: WordPress
X-Redirect-By: WordPress
< X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
< Location: https://www.vanassibara.com/
Location: https://www.vanassibara.com/
< Access-Control-Allow-Origin: *
Access-Control-Allow-Origin: *

(... more information about the reply ...)

Can you check with any of your images? I check it with a .png image from your website, but as png is not on the list, the header is not added.

curl -vLI "https://media.vanassibara.com/wp-content/uploads/20200506161720/Nothing-Diego-Vanassibara-Q.png"

Checking with the plugin developers may be a good idea too, so they can give you more information on what the plugin is expecting in the Apache configuration and also some way for better debugging it. I didn't find any related message in the Apache logs

gotzon 2020-05-20 11:36:32 UTC #7

@gongomgra hi!

Would you be so kind to try this below page?

https://www.vanassibara.com/e-store/dv065-feet-m/

In Chrome console, I am still getting the below error:
(index):1 Access to image at 'https://media.vanassibara.com/wp-content/uploads/20200506180209/DV065-Feet-Diego-Vanassibara-T.svg' from origin 'https://www.vanassibara.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
(index):1 GET https://media.vanassibara.com/wp-content/uploads/20200506180209/DV065-Feet-Diego-Vanassibara-T.svg net::ERR_FAILED

In file /opt/bitnami/apps/wordpress/conf/httpd-app.conf, does the section <Directory "/opt/bitnami/apps/wordpress/htdocs"> get applied to all my wordpress pages?

I will be very grateful for your thoughts on this.
Thank you for your help.

gongomgra 2020-05-21 09:45:46 UTC #8

Hi @gotzon,

I see you are using CloudFront to server your site. Can you check if you need to do any configuration related to CORS there?

$ curl -vLI "https://media.vanassibara.com/wp-content/uploads/20200506180209/DV065-Feet-Diego-Vanassibara-T.svg"

< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Content-Type: image/svg+xml
Content-Type: image/svg+xml
< Content-Length: 396
Content-Length: 396
< Connection: keep-alive
Connection: keep-alive
< Date: Wed, 20 May 2020 11:42:14 GMT
Date: Wed, 20 May 2020 11:42:14 GMT
< Last-Modified: Wed, 06 May 2020 18:02:10 GMT
Last-Modified: Wed, 06 May 2020 18:02:10 GMT
< ETag: "727c9dfc15965850bf5e72d50754b1ca"
ETag: "727c9dfc15965850bf5e72d50754b1ca"
< Cache-Control: max-age=31536000
Cache-Control: max-age=31536000
< Content-Encoding: gzip
Content-Encoding: gzip
< Expires: Thu, 06 May 2021 18:02:09 GMT
Expires: Thu, 06 May 2021 18:02:09 GMT
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Server: AmazonS3
Server: AmazonS3
< X-Cache: Miss from cloudfront
X-Cache: Miss from cloudfront
< Via: 1.1 7dc4818c830423900ae855831181d2b8.cloudfront.net (CloudFront)
Via: 1.1 7dc4818c830423900ae855831181d2b8.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: IAD89-C1
X-Amz-Cf-Pop: IAD89-C1
< X-Amz-Cf-Id: hvESrO2T1wDDcpBEYllUu8cIlaFPsmXGYnwNzx1x5gE-gRAjMuBHTw==
X-Amz-Cf-Id: hvESrO2T1wDDcpBEYllUu8cIlaFPsmXGYnwNzx1x5gE-gRAjMuBHTw==

I found a related topic in Stackoverflow in case it is of help. You may also want to check it with the plugins developers or the AWS support team.

gotzon 2020-05-23 18:34:04 UTC #9

@gongomgra this worked!

Following the above topic in Stackoverflow and these AWS instructions, I was able to set up CORS for my S3 bucket and Cloudflare distribution. I had not understood CORS needs to be set up on both sides.

Your help is super appreciated!

gongomgra 2020-05-25 08:51:25 UTC #10

Hi @gotzon,

Thanks for the info. I'm glad you fixed your issue! We will close this thread as solved. Please do not hesitate to open a new one with any other questions you may have.

gongomgra 2020-05-25 08:51:29 UTC #11

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!