QuestionQ41

VerifiedTroubleshoot infrastructure and configuration issues

Development of an Adobe Commerce website has been completed, and the website is ready for rollout to the production environment.

An Architect designed the system to operate in a distributed architecture with multiple backend webservers processing requests behind a Load Balancer.

After the system is deployed and the website is accessed for the first time, users cannot access the Customer Dashboard after signing in. The website continually redirects users to the sign-in page even though 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

A load-balanced multi-webserver deployment requires every backend to access the same session store. Configuring the Redis host as 127.0.0.1 makes each backend use its own local Redis instance, so a request routed to a different backend cannot retrieve the authenticated session. Configure the session Redis host to use a shared Redis instance reachable by all webservers. Adobe Commerce supports Redis as session storage and configures its host through the Redis session-storage settings.

Learn more

Community Discussion

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