Open James7665 opened 1 month ago
What are the logs from the backend and the browser console?
same problem, deployed on repocloud
What are the logs from the backend and the browser console?
What are the logs from the backend and the browser console?
Seems like you changed the port for the backend and didn't updated it in the docker compose or forgot to rebuild the images
Same problem, deployed by docker,
sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 13ecc68c23ba perplexica_perplexica-frontend "docker-entrypoint.s…" 24 seconds ago Up 23 seconds 0.0.0.0:3077->3000/tcp, :::3077->3000/tcp perplexica_perplexica-frontend_1 8a5399bd7550 perplexica_perplexica-backend "docker-entrypoint.s…" 24 seconds ago Up 24 seconds 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp perplexica_perplexica-backend_1
Same problem, deployed by docker,
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, then run the docker-compose down command, and then use docker-compose up -d --build to rebuild the docker image
sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 13ecc68c23ba perplexica_perplexica-frontend "docker-entrypoint.s…" 24 seconds ago Up 23 seconds 0.0.0.0:3077->3000/tcp, :::3077->3000/tcp perplexica_perplexica-frontend_1 8a5399bd7550 perplexica_perplexica-backend "docker-entrypoint.s…" 24 seconds ago Up 24 seconds 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp perplexica_perplexica-backend_1
Did you changed the ports for the IP provided as Args. to the frontend service?
Same problem, deployed by docker,
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, then run the docker-compose down command, and then use docker-compose up -d --build to rebuild the docker image
sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 13ecc68c23ba perplexica_perplexica-frontend "docker-entrypoint.s…" 24 seconds ago Up 23 seconds 0.0.0.0:3077->3000/tcp, :::3077->3000/tcp perplexica_perplexica-frontend_1 8a5399bd7550 perplexica_perplexica-backend "docker-entrypoint.s…" 24 seconds ago Up 24 seconds 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp perplexica_perplexica-backend_1
Did you changed the ports for the IP provided as Args. to the frontend service?
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, Other than that, no changes have been made
Same problem, deployed by docker,
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, then run the docker-compose down command, and then use docker-compose up -d --build to rebuild the docker image
sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 13ecc68c23ba perplexica_perplexica-frontend "docker-entrypoint.s…" 24 seconds ago Up 23 seconds 0.0.0.0:3077->3000/tcp, :::3077->3000/tcp perplexica_perplexica-frontend_1 8a5399bd7550 perplexica_perplexica-backend "docker-entrypoint.s…" 24 seconds ago Up 24 seconds 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp perplexica_perplexica-backend_1
Did you changed the ports for the IP provided as Args. to the frontend service?
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, Other than that, no changes have been made
Same problem, deployed by docker,
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, then run the docker-compose down command, and then use docker-compose up -d --build to rebuild the docker image
sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 13ecc68c23ba perplexica_perplexica-frontend "docker-entrypoint.s…" 24 seconds ago Up 23 seconds 0.0.0.0:3077->3000/tcp, :::3077->3000/tcp perplexica_perplexica-frontend_1 8a5399bd7550 perplexica_perplexica-backend "docker-entrypoint.s…" 24 seconds ago Up 24 seconds 0.0.0.0:3001->3001/tcp, :::3001->3001/tcp perplexica_perplexica-backend_1
Did you changed the ports for the IP provided as Args. to the frontend service?
Only change the docker-compose.yaml file, change the ports: - 3000:3000 to 3077:3000, Other than that, no changes have been made
You need to update the IP here:
Then re-build fresh images
You need to update the IP here:
Then re-build fresh images
You need to update the IP here:
Then re-build fresh images
Is it set to the current server's IP? For example 192.168.17.2:3001 ? Thank you very much!
You need to update the IP here: Then re-build fresh images
You need to update the IP here: Then re-build fresh images
Is it set to the current server's IP? For example 192.168.17.2:3001 ? Thank you very much!
Yes, set it to the server's IP
I was facing similar issues when trying to run on a different port. Here's the configuration that works for me:
docker-compose.yml
services:
searxng:
image: docker.io/searxng/searxng:latest
volumes:
- ./searxng:/etc/searxng:rw
ports:
- 4000:8080
networks:
- perplexica-network
perplexica-backend:
build:
context: .
dockerfile: backend.dockerfile
args:
- SEARXNG_API_URL=http://searxng:8080
depends_on:
- searxng
ports:
- 3002:3002
networks:
- perplexica-network
perplexica-frontend:
build:
context: .
dockerfile: app.dockerfile
args:
- NEXT_PUBLIC_API_URL=http://127.0.0.1:3002/api
- NEXT_PUBLIC_WS_URL=ws://127.0.0.1:3002
depends_on:
- perplexica-backend
ports:
- 3043:3000
networks:
- perplexica-network
networks:
perplexica-network:
config.toml
[GENERAL]
PORT = 3002 # Port to run the server on
SIMILARITY_MEASURE = "cosine" # "cosine" or "dot"
[API_KEYS]
OPENAI = "" # OpenAI API key - sk-1234567890abcdef1234567890abcdef
GROQ = "" # Groq API key - gsk_1234567890abcdef1234567890abcdef
[API_ENDPOINTS]
SEARXNG = "http://localhost:4000" # SearxNG API URL
OLLAMA = "http://host.docker.internal:11434" # Ollama API URL - http://host.docker.internal:11434
After changing these, re-build the images using docker compose up -d --build
and it should work.
Describe the bug A clear and concise description of what the bug is.
Based on the instructions, I installed using Docker, modified the tsconfig.json file, adding only the GROQ Key. After starting, the Homepage fails to load. However, when testing port 31336, searxng is accessible.
Screenshots