ERR_TOO_MANY_REDIRECTS error when accessing Magento 2 shop backend on AWS image

lemkd_bitnami 2018-06-11 11:46:27 UTC #1

Keywords: Magento - Amazon Web Services - Technical issue - Other
Description:
Platform: AWS
Image: Community AMI, Magento 2.2.4 (ami-78414701)

Steps to reproduce:
* spawn the AWS instance with the image above
* run the following commands to install sample data on the shop

cd /opt/bitnami/apps/magento/htdocs/
sudo touch auth.json
sudo chown bitnami:bitnami auth.json
echo ' { "http-basic": {  "repo.magento.com": { "username": "xxxx", "password": "xxx" } } }' > auth.json
sudo composer update
sudo bin/magento-cli sampledata:deploy
sudo bin/magento-cli setup:upgrade
sudo bin/magento-cli setup:di:compile
sudo bin/magento-cli cache:flush

access the backend of the instance via https://<IP>/admin

When using Chrome, I will now receive an ERR_TOO_MANY_REDIRECTS error. In Edge this seems to be working fine. This is pretty much identical to the following thread, which doesn't really provide a solution for the problem though:

jota 2018-06-12 08:27:22 UTC #4

Hi @lemkd_bitnami,

Instead of running the commands you posted, could you please run these ones?

cd /opt/bitnami/apps/magento/htdocs/
sudo touch auth.json
sudo chown bitnami:bitnami auth.json
echo ' { "http-basic": {  "repo.magento.com": { "username": "xxxx", "password": "xxx" } } }' > auth.json
sudo chown daemon:daemon auth.json
sudo composer update
sudo chown -R daemon:daemon ./
sudo bin/magento-cli sampledata:deploy
sudo bin/magento-cli setup:upgrade
sudo bin/magento-cli setup:di:compile
sudo bin/magento-cli cache:flush

The permissions of the Magento folder are set to daemon:daemon so you need to restore the permissions in case you run any command with sudo (the magento-cli tool uses the daemon user)

We have a Support Tool that will gather relevant information for us to debug the issue. Could you please download and execute it on the machine where the stack is running by following the steps described in the guide below?

How to Run the Bitnami Support Tool

Please note that you need to paste the code outputted by the tool in your reply.

lemkd_bitnami 2018-06-12 09:22:16 UTC #5

I've set the ownership to daemon:daemon after executing the magento-cli commands but still encounter the problem. The ID from the support tool: 694b932b-92bd-50b9-25f4-ad80c535b219

Thanks,
Daniel

crhernandez 2018-06-19 08:55:10 UTC #6

Hi,

the fact that it works in Edge but not in Chrome is weird, can you try using the Private mode in Chrome?

1.- On your computer, open Chrome.
2.- At the top right, click on the three vertical dots and then New Incognito Window.
3.- A new window appears. In the top corner, check for the Incognito icon.

You can also use a keyboard shortcut to open an Incognito window:
- Windows, Linux or Chrome OS: Press Ctrl + Shift + n.
- Mac: Press ⌘ + Shift + n.

I just checked the logs shared by the bnsupport tool. In the apache logs, I can't see any significant issue, but in the magento exceptions logs I can see the following lines:

[2018-06-11 11:29:24] main.CRITICAL: 5.7.8 Username and Password not accepted. Learn more at
 5.7.8  https://support.google.com/mail/?p=BadCredentials f25-v6sm21964327edd.87 - gsmtp
 {"exception":"[object] (Magento\\Framework\\Exception\\MailException(code: 0): 5.7.8 Username and Password not accepted. Learn more at
 5.7.8  https://support.google.com/mail/?p=BadCredentials f25-v6sm21964327edd.87 - gsmtp
 at /opt/bitnami/apps/magento/htdocs/app/code/MagePal/GmailSmtpApp/Plugin/Mail/TransportPlugin.php:121, Zend_Mail_Protocol_Exception(code: 535): 5.7.8 Username and Password not accepted. Learn more at
 5.7.8  https://support.google.com/mail/?p=BadCredentials f25-v6sm21964327edd.87 - gsmtp
 at /opt/bitnami/apps/magento/htdocs/vendor/magento/zendframework1/library/Zend/Mail/Protocol/Abstract.php:431)"} []

According to the date and time (2018-06-11 11:29:24), would it fit with the changes done by you?

Best regards,
Carlos R. Hernández

lemkd_bitnami 2018-06-20 10:39:56 UTC #7

I've tried it with private mode in Chrome, still the same problem. I also tried Firefox (not working) and IE (working). Please find the comparison along with version numbers below.

The error in the logs doesn't seem to be related. I removed all log files, reproduced the problem and there were no exceptions in the log afterwards.

crhernandez 2018-06-21 09:46:57 UTC #8

Hi,

Unfortunately, we were unable to reproduce the issue. I followed the steps indicated in the first post

lemkd_bitnami:

sudo touch auth.json
sudo chown bitnami:bitnami auth.json
echo ' { "http-basic": {  "repo.magento.com": { "username": "xxxx", "password": "xxx" } } }' &gt; auth.json
sudo composer update
sudo bin/magento-cli sampledata:deploy
sudo bin/magento-cli setup:upgrade
sudo bin/magento-cli setup:di:compile
sudo bin/magento-cli cache:flush

and everything worked correctly, at this moment I have the sample data accessing using Chrome:

I tried using two different Magento instances, one launched by the Bitnami Google Launchpad and the other by the Bitnami AWS Launchpad; both cases works fine.

Also, I did a third attempt using a community AMI: Magento 2.2.4-1 (ami-78414701) in EU (Ireland). It works fine:

Can you send me by a Direct Message your IP to continue with the checks?

Best regards,
Carlos R. Hernández

crhernandez 2018-06-21 10:11:03 UTC #9

Hi @lemkd_bitnami,

I think that I have found the reason and the solution for this issue.

The problem is that if you access to Admin using HTTP (http://<IP>/admin) it works fine, but accessing via HTTPS (https://<IP>/admin) it fails. According to the screenshots, those browsers in which it works is because it is being accessed with HTTP instead of HTTPS. It may be that internally some browsers automatically redirect the HTTP traffic to HTTPS for the admin page or something similar.

Really this is not an issue, it is the way Magento is configured. We provide everything necessary to use HTTPS, but it is an option that must be enabled from the Magento configuration through its web interface. To enable this option:

From the dashboard, go to stores -> configuration
Inside General section, go to Web
Once Web section is loaded, click on Base URLs (Secure) and choose Yes in Use Secure URLs in Admin
Click on Save Config
After that, you should follow the link in the warning popup message and click on Flush Magento Cache

After that, you should be able to access to the admin panel using HTTP/HTTPS.

Please let us know if this solves the issue.

Best regards,
Carlos R. Hernández

lemkd_bitnami 2018-06-22 05:46:24 UTC #10

That indeed solved the problem. Thank you so much Carlos and team, awesome support!

Kind regards,
Daniel

crhernandez 2018-06-22 07:42:28 UTC #11

Hi,

We are glad that you were able to fix the issue We are marking the previous answer as “Solution” and this topic as “Closed".
If you have any other questions, please do not hesitate to let us know. Feel free to create a new topic referencing to this one if necessary.

Best regards,
Carlos R. Hernández

crhernandez 2018-06-22 07:42:37 UTC #12

Powered by Discourse, best viewed with JavaScript enabled

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

SugarCRM

Drupal

WordPress

Joomla!

Redmine