Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: unable to login after deploy #1618

Closed
cyberlink1 opened this issue Jun 6, 2024 · 1 comment
Closed

[BUG]: unable to login after deploy #1618

cyberlink1 opened this issue Jun 6, 2024 · 1 comment
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.

Comments

@cyberlink1
Copy link
Contributor

How are you running AnythingLLM?

Docker (remote machine)

What happened?

I deployed into my docker swarm with the attached docker-compose.
Initial setup goes well, I can get to the web page and into the first workspace but after a minute or so everything stops working, reloading the page throughs me out to the login screen.
Any attempt to login after that I get "Error: Could not validate login."

The log file shows

[Event Logged] - login_event
Cannot create JWT as JWT_SECRET is unset. Error: Cannot create JWT as JWT_SECRET is unset.
at makeJWT (/app/server/utils/http/index.js:21:11)
at /app/server/endpoints/system.js:205:18

The .env file is there and does contain a JWT_SECRET.

I will note that when it kicks me out, it is actually the container crashing with

[Event Logged] - workspace_created
[TELEMETRY SENT] {
event: 'onboarding_complete',
distinctId: '931920d5-6bf2-4c6d-aea4-31ec594a3272',
properties: { runtime: 'docker' }
}
/usr/local/bin/docker-entrypoint.sh: line 7: 118 Illegal instruction (core dumped) node /app/server/index.js

anythingllm.zip

Are there known steps to reproduce?

No response

@cyberlink1 cyberlink1 added the possible bug Bug was reported but is not confirmed or is unable to be replicated. label Jun 6, 2024
@cyberlink1
Copy link
Contributor Author

cyberlink1 commented Jun 6, 2024

Never mind this was caused by the CPU not having the AVX flag.

#1331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.
Projects
None yet
Development

No branches or pull requests

1 participant