Fix WaSphere Session Login Bug

Employer not named by the sourceRemote

Full Stack

Apply on the company’s site

Frontier is not the employer and does not collect applications.

About this role

Linux, Shell Script, Docker, API, DevOps · The WaSphere dashboard running on my production server (Alma Linux 9+Cyberpanel, public link: http://177…:3004/login) throws the alert “Your session has expired. Please log in again” every time I try to sign in with a freshly-created user.

Over the past week I have: • SSH’d into the machine, opened the WaSphere directory, and tweaked both the .env and docker-compose.yml files. • Brought the stack back up with `docker compose up -d`. • Added an Nginx adjustment that I thought would help.

Despite these changes the session error persists, so I’m convinced an overlooked or incorrect configuration is still blocking proper authentication.

You will have direct SSH access, the edited .env and docker-compose.yml snippets, plus a short screen-capture video that shows the exact failure path.

Deliverables 1. Diagnose the root cause (environment variables, Docker service, Nginx proxy, or anything else). 2. Apply and document the fix so I can reproduce it on staging and future deployments. 3. Confirm that login sessions remain valid through multiple browser refreshes.

If you’ve untangled Docker-based auth issues before, this should be straightforward. I’m ready to provide an