Closed perlinson closed 2 months ago
You need to change the IP in the docker-compose file to the private IP of the server where you deployed Perplexica.
which one to change and where to change?
here?
here?
Looks perfect
it got this problem
by the way
this proxy setting work well, but it's wrong when i use the
i was using ubuntu 22.04 os
i was solve the proxy problem, just left the "Access-Control-Allow-Origin" problem
I've already implemented CORS on the backend server, so it should not produce errors like this. We only provide installation support in Perplexica. If you wish to expose it to your network, you should have sufficient knowledge to do so on your own, and therefore, we cannot assist you with that.
Sorry, I still get trouble at this issue. I have changed ip, but still can't access it from another pc on the LAN. (Home page keeps loading)
... ...
- NEXT_PUBLIC_API_URL=http://192.168.31.19:3001/api
- NEXT_PUBLIC_WS_URL=ws://192.168.31.19:3001
... ...
docker-compose.yaml
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:
- 3001:3001
networks:
- perplexica-network
perplexica-frontend:
build:
context: .
dockerfile: app.dockerfile
args:
- NEXT_PUBLIC_API_URL=http://192.168.31.19:3001/api
- NEXT_PUBLIC_WS_URL=ws://192.168.31.19:3001
depends_on:
- perplexica-backend
ports:
- 3000:3000
networks:
- perplexica-network
networks: perplexica-network:
Describe the bug A clear and concise description of what the bug is. work on localhost:3000port , when i use a domain:3000 , on remote pc ,it not work , i use local ollama To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.