QuestionQ31

VerifiedStore Operations and Admin

Development of an Adobe Commerce website is complete, and the website is ready for deployment to the production environment.

An Architect designed the system to operate in a distributed architecture consisting of multiple backend webservers that handle requests behind a Load Balancer.

After deploying the system and visiting the website for the first time, users cannot access the Customer Dashboard after they log in. The website continually redirects users to the sign-in page, although they have logged in successfully. The Architect determines that the session is not being saved correctly.

In app/etc/env.php, the session is configured as follows:

Question Image

What should the Architect do to resolve this issue?

Explanation

In a multiple-web-node Adobe Commerce deployment, session data must be available to every backend server. The address 127.0.0.1 refers to the local machine, so each webserver uses its own Redis endpoint and authenticated sessions are not shared across load-balanced requests. Configure the Redis session host as a shared Redis instance reachable by all webservers. Adobe recommends Redis for sessions in multiple-web-node deployments and documents the Redis host setting for session storage.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!