Dokploy / Dokploy/dokploy

Session Expiry Not Detected – Environment Variable Save Fails with Generic Error Instead of Redirecting to Login

Open
#4,310 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

To Reproduce
  1. Log into Dokploy dashboard
  2. Navigate to a service → Environment Variables
  3. Leave the session idle until it expires
  4. Attempt to add or update environment variables
  5. Click save
Current vs. Expected behavior

Current behavior:

  • Saving environment variables fails with a generic “error” message
  • No indication that the session has expired
  • User remains on the same screen with no recovery guidance

Expected behavior:

  • Detect expired session before or during the request

Either:

  • Automatically redirect to login screen, or
  • Show a clear message like “Session expired, please log in again”

Prevent silent failure when saving configuration.

Provide environment information
Operating System:
OS: Ubuntu 24.04
Arch: amd64

Dokploy version: v0.29.2
VPS Provider: Fasthosts
Application: licenseapi (Docker Compose deployment)
Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context
  • The issue only became clear after manually refreshing the page, which then redirected to the login screen
  • Prior to refresh, the UI appeared fully functional but all save actions failed
  • This led to confusion and incorrect debugging of deployment/config issues
Will you send a PR to fix it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named in the issue. Start by reproducing the expired-session save flow for Environment Variables and trace the dashboard request and session handling; done means the save attempt either redirects to login or clearly reports that the session expired instead of showing a generic error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, nextjs, typescript
Domain
authentication, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.