Version Conflict: Docker Upgrade to 0.7.6 Downgrades to 0.7.5 and Causes Login Issues

[hhh2210]

🐛 Version Conflict/Configuration Issue: Applying Unsecured HTTP Fix with docker compose up -d Downgrades to 0.7.5 and Causes Login Issues

Environment:

• Operating System: LINUX Remote Server
• LibreChat Version: Already upgraded to 0.7.6 (latest version in official documentation), attempting to apply unsecured HTTP fix
• Deployment Method: Docker (official documentation recommended)

Problem Description:

I followed the official documentation (Fixing Unsecured HTTP Connections) to apply the unsecured HTTP fix using the docker compose up -d command. However, I encountered the following two issues, suspecting a version conflict or configuration problem during the fix application process:

Issue 1: Using docker compose up -d command to apply the fix automatically downgrades to version 0.7.5

• Steps to reproduce: Following the official documentation, I used the docker compose up -d command to apply the unsecured HTTP fix.
• Expected result: Successfully apply the unsecured HTTP fix, LibreChat version should remain at 0.7.6 or higher.
• Actual result: LibreChat automatically downgraded back to version 0.7.5 and used the backend:dev branch. My override.yml configuration remained effective, and refreshing the page did not require re-login.
• Log information:

[email protected] backend

cross-env NODE_ENV=development npx nodemon api/server/index.js

npm warn exec The following package was not found and will be installed: [email protected]

Issue 2: Deploying 0.7.6 version using npm run start:deployed requires re-login after refreshing the page (unrelated to Issue 1, for comparison)

• Steps to reproduce: I used the npm run start:deployed command, which executes the deploy-compose.yml file for deployment, to ensure the current version is 0.7.6. (This step is not related to the unsecured HTTP fix, but used for comparison to observe login behavior in version 0.7.6)
• Expected result: LibreChat remains at version 0.7.6 and should not require re-login for continued use.
• Actual result: LibreChat remains at version 0.7.6, but refreshing the page forcefully requires re-login.
• Log information: (Same as before, omitted here)

2025-02-10 10:42:52 [32minfo [39m: [32m[Optional] Redis not initialized. Note: Redis support is experimental. [39m
... (Omitted other log information) ...
2025-02-10 10:43:01 [32minfo [39m: [32mServer listening on all interfaces at port 3080. Use http://localhost:3080 to access it [39m

Screenshot:

(Please describe the screenshot content, e.g., Screenshot shows the login page after upgrade)

Expectations:

• Using the officially recommended docker compose up -d command to apply the unsecured HTTP fix should not downgrade the version and should maintain existing configurations and login status.
• Applying the unsecured HTTP fix should not result in version downgrading or a forced re-login.

Possible Causes (Speculation):

• The docker compose up -d command for applying the unsecured HTTP fix might be pulling an incorrect image version or branch by default (e.g., backend:dev), causing the downgrade.
• Version 0.7.5 (backend:dev branch) might have differences in login state management compared to version 0.7.6.
• The unsecured HTTP fix process might unintentionally affect the persistence of login state.

Please help the development team investigate and resolve this issue. Thank you!

[hhh2210]

Upon executing the commands:

docker compose -f deploy-compose.yml -f docker-compose.override.yml pull
docker compose -f deploy-compose.yml -f docker-compose.override.yml up

as documented at https://www.librechat.ai/docs/configuration/docker_override#deploy-composeyml, Docker fails to initiate. The error logs reveal:

npm error Lifecycle script `backend:dev` failed with error:
npm error workspace @librechat/[email protected]
npm error location /app/api
npm error Missing script: "backend:dev"


To see a list of scripts, run:
npm error npm run --workspace=@librechat/[email protected]
npm error Lifecycle script `backend:dev` failed with error:
npm error workspace @librechat/[email protected]
npm error location /app/api
npm error Missing script: "backend:dev"

This indicates a missing backend:dev script within the @librechat/backend workspace.

[danny-avila]

Issue 1: Using docker compose up -d command to apply the fix automatically downgrades to version 0.7.5

Follow these instructions to update LibreChat with docker (or corresponding commands for deploy-compose.yml): https://www.librechat.ai/docs/local/docker#update-librechat

as documented at https://www.librechat.ai/docs/configuration/docker_override#deploy-composeyml, Docker fails to initiate. The error logs reveal:

Do you have the project cloned down? I use these commands almost daily (via npm run update:deployed) without issues.

Issue 2: Deploying 0.7.6 version using npm run start:deployed requires re-login after refreshing the page (unrelated to Issue 1, for comparison)

This is a symptom of using localhost or insecure connection in an express.js app, you need HTTPS to prevent this.

[hhh2210]

I'm currently using remote hosting at LINUX, so the updating process would be this:
| https://www.[librechat.ai/docs/remote/docker_linux](https://www.librechat.ai/docs/remote/docker_linux
I've already tried to update but the 0.7.6 seems to can't handle deploy-compose-overide.yml properly.

And i think this commend "npm run update:deployed" already clone the whole project down.
What really confusing me is that it seems i can't have 0.7.6 and cookie seeting at the same time.（As i mentioned before, the official doc https://www.librechat.ai/blog/2024-05-16_unsecured_http require to modify the deploy-compose-overide.yml）