Magento redirect loop after updating

:warning: IMPORTANT, please fill the questions

We assume you are using Bitnami to deploy your application.

  • Which version of the application are you using?: Latest version

  • Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, …) or VM (VMDK, VBOX): deployed to AWS Lightsail

  • Have you installed any plugin or modified any configuration file?: It can not be done , does not work

  • Describe here your question/suggestion/issue (expected and actual results): I can run up the image and see initial store front, login to back end and put in products.
    There is however not possibility to load modules, template or logos or update (Magento keys are in place, and mode changed to production) GUI method stops on “Component dependency fail” I have not found more detailed info on the fail, I can not even upload my Company logo.
    Then I went the CLI way Updates first The Debian OS the Magento updates ran as expected but after I can not connect to the site get endless redirect loop.
    I have spent 2 days trying to work this out trying over and over again from scratch or restored snap shots it even seems that AWS Lightsail snapshots are useless since after restore fully working snapshot goes straight to redirect loop.
    The unusual non standard directory arrangement really makes all fault finding harder and more complicated.

  • Steps to reproduce the issue (if relevant): Set up Magento instance on Lightsail an try to update - upload - etc

  • Copy the apache log (if relevant):

access.log
127.0.0.1 - - [01/Apr/2019:18:29:34 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:29:38 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:29:43 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:29:48 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:29:53 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:29:58 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:30:03 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:08 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:13 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:18 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:23 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:30:28 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:33 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:38 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:43 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:48 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:30:53 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:30:58 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:31:03 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:31:08 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:31:13 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1 - - [01/Apr/2019:18:31:18 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
 
error.log:
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:29:59 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:03 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:08 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:13 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:18 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:23 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:24 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:28 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:33 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:38 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:43 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:48 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:49 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:53 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:30:58 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:03 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:08 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:13 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "POST /setup/index.php/session/prolong HTTP/1.1" 302 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:14 +0000] "GET /setup/index.php/session/unlogin HTTP/1.1" 401 4374
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ 127.0.0.1 - - [01/Apr/2019:18:31:18 +0000] "GET /pub/health_check.php HTTP/1.1" 200 -
127.0.0.1: command not found
bitnami@ip-172-26-1-20:~$ ^C
bitnami@ip-172-26-1-20:~$ sudo tail -n100 /opt/bitnami/apache2/logs/error_log
[Mon Apr 01 09:30:00.089850 2019] [authz_core:error] [pid 17260:tid 139652497352448] [client 127.0.0.1:36968] AH01630: client denied by server configuration: /opt/bitnami/apps/magento/htdocs/app/etc/config.php
[Mon Apr 01 09:45:28.897007 2019] [authz_core:error] [pid 17260:tid 139652212000512] [client 127.0.0.1:37432] AH01630: client denied by server configuration: /opt/bitnami/apps/magento/htdocs/app/etc/config.php
[Mon Apr 01 17:19:04.282291 2019] [ssl:warn] [pid 1933:tid 139985881573120] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:19:04.683756 2019] [ssl:warn] [pid 1934:tid 139985881573120] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:19:04.701870 2019] [mpm_event:notice] [pid 1934:tid 139985881573120] AH00489: Apache/2.4.37 (Unix) OpenSSL/1.0.2q configured -- resuming normal operations
[Mon Apr 01 17:19:04.701902 2019] [core:notice] [pid 1934:tid 139985881573120] AH00094: Command line: '/opt/bitnami/apache2/bin/httpd.bin -f /opt/bitnami/apache2/conf/httpd.conf'
[Mon Apr 01 17:30:21.134896 2019] [mpm_event:notice] [pid 1934:tid 139985881573120] AH00491: caught SIGTERM, shutting down
[Mon Apr 01 17:31:46.396331 2019] [ssl:warn] [pid 1906:tid 140630884882176] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:31:46.474072 2019] [ssl:warn] [pid 1907:tid 140630884882176] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:31:46.492316 2019] [mpm_event:notice] [pid 1907:tid 140630884882176] AH00489: Apache/2.4.37 (Unix) OpenSSL/1.0.2q configured -- resuming normal operations
[Mon Apr 01 17:31:46.492349 2019] [core:notice] [pid 1907:tid 140630884882176] AH00094: Command line: '/opt/bitnami/apache2/bin/httpd.bin -f /opt/bitnami/apache2/conf/httpd.conf'
[Mon Apr 01 17:52:38.031118 2019] [mpm_event:notice] [pid 1907:tid 140630884882176] AH00491: caught SIGTERM, shutting down
[Mon Apr 01 17:54:02.137258 2019] [ssl:warn] [pid 1922:tid 140457742616320] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:54:02.292370 2019] [ssl:warn] [pid 1923:tid 140457742616320] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:54:02.342528 2019] [mpm_event:notice] [pid 1923:tid 140457742616320] AH00489: Apache/2.4.37 (Unix) OpenSSL/1.0.2q configured -- resuming normal operations
[Mon Apr 01 17:54:02.342561 2019] [core:notice] [pid 1923:tid 140457742616320] AH00094: Command line: '/opt/bitnami/apache2/bin/httpd.bin -f /opt/bitnami/apache2/conf/httpd.conf'
[Mon Apr 01 17:56:18.507557 2019] [mpm_event:notice] [pid 1923:tid 140457742616320] AH00491: caught SIGTERM, shutting down
[Mon Apr 01 17:56:49.752293 2019] [ssl:warn] [pid 3279:tid 140536670459648] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:56:49.807375 2019] [ssl:warn] [pid 3280:tid 140536670459648] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Apr 01 17:56:49.833639 2019] [mpm_event:notice] [pid 3280:tid 140536670459648] AH00489: Apache/2.4.37 (Unix) OpenSSL/1.0.2q configured -- resuming normal operations
[Mon Apr 01 17:56:49.833680 2019] [core:notice] [pid 3280:tid 140536670459648] AH00094: Command line: '/opt/bitnami/apache2/bin/httpd.bin -f /opt/bitnami/apache2/conf/httpd.conf'

uploded bitnami support analysis see code ef9e1025-b945-99bf-5fc7-eea6b0eae02e

Hi @martolvan,

Did you make any change in the conf files or the permissions inside the installation before running into this issue?

We include a modified cli script to not break the installation’s permissions in the application, did you use it?

https://docs.bitnami.com/aws/apps/magento/administration/using-magento-cli/

If you didn’t, can you recover the permissions of the installation by running these commands

sudo chown -R daemon:daemon /opt/bitnami/apps/magento/htdocs
sudo chmod -R g+w /opt/bitnami/apps/magento/htdocs

Let us know if that solves the problems.

No I did not and I have only followed instructions fun on bitnami current image is an restored snapshot, where nothing but some system adjustments in Magento GUI have been done.

I used apt for OS and then some CLI commands found in bitnami forum I]m not shure if it was the intended script or not.

Has no effect, same thing.

Regards Stefan

In meantime I set up VMware ESXi free 6.7 on local computer and ran ir up since it is located on dedicated server network I do not have dhcp server on there since all devices are fixed ip.
How ever directions on that issue https://docs.bitnami.com/virtual-machine/faq/configuration/configure-static-address/ do not work and there is some deviation on implementation from standard Debian so instructions from there do not work either.
I know that this is an separate issue but still empasises that somethig is not right with the image witch is the same but for different platform.
I find it awfully strange that it seems so hard to make this work.

Regards Stefan

Has any one been able to deploy the current bitnami image ?

Hi @martolvan, we could launch a Bitnami Magento OVA successfully.

Regarding the issues you mention, first of all, it seems you mentioned updating the Debian OS. Bitnami images on Lightsail use Ubuntu 16.04, not Debian 9. Could you confirm you are using a Bitnami image on Lightsail?

In addition to this, in Bitnami Lightsail images, there is a bug preventing users from connecting to SSH after the upgrade finished and restarted the instances. Check this thread for more info.

Finally, in order to understand your redirection loop, could you run the command below in your command line interface?

curl -vvv http://yourdomain.com

(where http://yourdomain.com is the url to your Magento installation)

Hi Marcos
I´m sorry my mistake it is indeed Ubuntu I sometimes mistake the two, they are very similar, this is the image:

Using username “bitnami”.
Authenticating with public key “imported-openssh-key”
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-1077-aws x86_64)
___ _ _ _
| _ |) | _ _ __ _ _ __ ()
| _ \ | | ’ / ` | ’ | |
|
/|_|||_,|||||

*** Welcome to the Bitnami Magento 2.3.0-0 ***
*** Documentation: https://docs.bitnami.com/aws/apps/magento/ ***
*** https://docs.bitnami.com/aws/ ***
*** Bitnami Forums: https://community.bitnami.com/ ***
Last login: Thu Apr 4 09:08:25 2019 from 85.220.116.10

On the redirect issue it seems to be back for the dead, I found that I had to do an database edit in order to get an snaphhot to work. an both front and Back end are on the AWS light sail working except for the update and module installs it always returns same error with little to none hints on what to do, the link that comes is an Magento community link that suggests checking per missions etc.
Earlier in this thread it was recommended to do thing bitnami way not the Magneto since paths permissions etc. are different. possibly I could find correct permission deviation and fix if I could find somewhere bit more detailed errors I cant find any thin of use in the logs Ive found under bitnami/apache2 logs or those logs I’ve found in Magento.
Regards Stefan

1 Like

Hi @martolvan, great to hear you were able to solve that issue!

Also, it seems you did not upgrade the Ubuntu OS to 18.04. That’s good, as it is known to break the startup (although a fix is mentioned in the link I posted).

Please let us know if you have any other questions, or if you find any other issues.

This issue still remains no modules or Magento updates will install through the intended Magento web setup method, and no real log or error messages more than in the “Readyness Check” it stops with this message: “Check Component Dependency. We found conflicting component dependencies. Hide detail For additional assistance, see component dependency help .”
These are all the details to be found, an why I did an OS update in hope that it might be an library update or some thing.

So image is useless can’t even add payment or other necessary modules.
PS. Even when all works I get weary of OS verison upgrades :wink:

Regards Stefan

Hi all
I have been trying more on the AWS docker machine. I still can not update an by doing this from CLI using directions from both Binami and Magento it is bit more verbose an I soon found that I had to change permission on /opt/bitnami/php/composer to 777, tha enabled me to go further, I could update the composer it self.
Now I tied to upgrade Magento from CLI and I seem to have probably an mix of conflicting configuration and file permissions. I get as far as being prompted for Magento repository permissions that should be User=public_key Pass=Private_key however I can only give user psaa can not be typed in. I then tried to figure out where from to run update, in hope that configuration from WebGUI would be in there.
After deleting drirectories from /opt/bitnami/php/composer/cache/repo
I can #:/opt/bitnami/apps/magento/htdocs/update/vendor/magento/composer$ sudo -u daemon /opt/bitnami/php/bin/composer.phar update and it seems to run and update, Magento web GUI still demands update and does not work.
So I still stick by the heading there are serious flaws in this image setup, that render it unusable, I do not believe that’s by intention but it is disappointing to spend days on trying to fix it, with out any luck.

Hi @martolvan, sorry for the delay.

First of all, I’m a bit confused. You’re mentioning AWS Docker machine but it seems you are using a Bitnami Single VM image. Could you clarify this?

Next, you can find the recommended upgrade instructions here: https://docs.bitnami.com/installer/apps/magento/administration/upgrade/

If you get any error, please let us know what you see. In addition to that, please run the support tool again.

Hi Marcos
That is easy to clarify, sin I had such an hard time getting the Docker image to work I tried to set up an ESXi machine from your image and that worked even worse since located on none dhcp network it seems impossible to give it an IP address.

So I abandoned that altogether and I’m fondling around with docker image on AWS, lets not divert to the other.

There is still no more progress, my latest take is setting all up on an stripped OS by myself hoping for better results, I wery disappointed though since I have used pre packaged bitnami images with excellent results before.

Frá: marcos answers@bitnami.com
Efni: [Bitnami Community] [Magento] Magento redirect loop after updating

[https://d2hzlohlg26lpl.cloudfront.net/user_avatar/community.bitnami.com/marcos/45/6814_1.png]

marcoshttps://community.bitnami.com/users/marcos
April 15

Hi @martolvanhttps://community.bitnami.com/users/martolvan, sorry for the delay.

First of all, I’m a bit confused. You’re mentioning AWS Docker machine but it seems you are using a Bitnami Single VM image. Could you clarify this?

Next, you can find the recommended upgrade instructions here: https://docs.bitnami.com/installer/apps/magento/administration/upgrade/

If you get any error, please let us know what you see. In addition to that, please run the support tool again.

Hi @martolvan, I’m still a bit confused with your message.

Why are you setting it up on a stripped OS? Why don’t you use a pre-packaged Bitnami image? If you get any errors, could you describe them to us?

Hi Marcos

I have already described the errors to you and I‘m not making progress on getting the bitnami Magento image to work.
Problem is that even though I can start up the image, log in to back end an see front end, it is still useless, since it is not possible to pass “Readiness Check” to install either updates or modules / extensions therefore payment right language etc cannot be added. It fails this “Readiness Check” test with the detailed error message ”We found conflicting component dependencies“ and no better info in logs or elsewhere where I have looked (practically all over the system) to be found I have found few directories using CLI update / install , all of wich I have written back to the thread.

I do realize that I probably could og for 777 on the whole of magento dir and php dir and all would work, however that would destroy the main reason for using Bitnami image the security and stability. This is why I try to start from scratch since in almost 2 weeks I have not been able to solve this.

Frá: marcos answers@bitnami.com
Efni: [Bitnami Community] [Magento] Magento redirect loop after updating

[https://d2hzlohlg26lpl.cloudfront.net/user_avatar/community.bitnami.com/marcos/45/6814_1.png]

marcoshttps://community.bitnami.com/users/marcos
April 16

Hi @martolvanhttps://community.bitnami.com/users/martolvan, I’m still a bit confused with your message.

Why are you setting it up on a stripped OS? Why don’t you use a pre-packaged Bitnami image? If you get any errors, could you describe them to us?

Hi @martolvan, thanks for the additional information, we were able to reproduce this issue.

The Magento Readiness Checks are failing when checking composer dependencies because of the PHP memory limit warning:

However, we understand this is not fully clear and users should ideally not see this warning. Therefore, for now we will work on the following:

  • Discuss on increasing the required memory of Magento instances (e.g. so you cannot launch AWS instances running Magento with less than 3 or 4 GB of memory).
  • Document how to workaround this issue in the update instructions.

In the meantime, you can fix this issue on your side by increasing the PHP memory_limit flag from 768M to 2GB in the following locations:

/opt/bitnami/php/etc/php.ini
/opt/bitnami/apps/magento/conf/php-fpm/php-settings.conf

After that restart Apache and PHP-FPM services:

sudo /opt/bitnami/ctlscript.sh restart apache
sudo /opt/bitnami/ctlscript.sh restart php-fpm

After that you should see no warnings in Magento’s Readiness Checks.

Hi Marco

Thank you this worked i had not found the /opt/bitnami/apps/magento/conf/php-fpm/php-settings.conf setting I know tha Im running this pilot project on minimum resources only 2GB memory light sail instance, but it seems to work now .

Thank you for your help through this caveat.

Best regards
Stefan B. Jonsson

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