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]: Got blank page after send a message #3018

Closed
mingtotti opened this issue Jan 24, 2025 · 3 comments
Closed

[BUG]: Got blank page after send a message #3018

mingtotti opened this issue Jan 24, 2025 · 3 comments
Labels
possible bug Bug was reported but is not confirmed or is unable to be replicated.

Comments

@mingtotti
Copy link

How are you running AnythingLLM?

Docker (local)

What happened?

Hi, I am using AnytingLLM with docker, and setup with DeepSeek, but got blank page after I send the message.
I just started learning NodeJS and have been looking for a solution for a long time but couldn’t find one. Please help me out.

bellow is the .env file

# Auto-dump ENV from system call on 11:31:56 GMT+0000 (Coordinated Universal Time)
LLM_PROVIDER='deepseek'
EMBEDDING_ENGINE='native'
VECTOR_DB='lancedb'
DEEPSEEK_API_KEY='sk-.......'
DEEPSEEK_MODEL_PREF='deepseek-chat'
STORAGE_DIR='/app/server/storage'
SIG_KEY='...'
SIG_SALT='....'

I got no error messages from docker logs, but got error messages from web console.

Image

Are there known steps to reproduce?

Image

@mingtotti mingtotti added the possible bug Bug was reported but is not confirmed or is unable to be replicated. label Jan 24, 2025
@shatfield4
Copy link
Collaborator

We have just patched this today via 9584a7e.

Please repull the docker image and it should be fixed now.

@mingtotti
Copy link
Author

We have just patched this today via 9584a7e.

Please repull the docker image and it should be fixed now.

@shatfield4 That fixed the issue, thanks!

@julienferga
Copy link

Hello, just a quick note about this issue: I experienced the same problem and tried everything yesterday, until I found this thread. Simply repulling the docker image resolved the issue. Many thanks!

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

3 participants