-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Failed to connect to the server #656
Comments
ollama api and searxng api works well. |
Hey please follow this: https://github.com/ItzCrazyKns/Perplexica/blob/master/docs/installation/NETWORKING.md Where you update your IP make sure it matches the port as well, it shall work. |
I have changed the docker-compose.yaml file. args:
But still not working. |
Have input the Ollama URL, that should be enough. [MODELS.OLLAMA] Otherwise I cannot open the web ui for the key setting. |
same error for me. Was running the docker compose as written in the turorial without changing any ports or settings. Ive only added my openai api key and renamed the toml.config file. |
Did you run |
Can you please provide logs from the browser console and the containers? |
Hi, i got same issues: hardcoded 127.0.0.1:3001 is inside .js files. My workoround: First -ensure everywhere in variables inside files fetched from git you changed variables to desired IP next build the app : then run console from frontend container:
instide container bash (replace yYOURVALIDIP with desired IP):
then commit changes done inside container
if you did a connection before -clear cache in your browser or try in private mode. |
Man, problem is inside .js files in web app. It probably everything works fine -when run from same machine, where perplexica is running. But when docker server is another machine and client connects via network -then issues starts to occur. |
Its not a problem but rather a feature of NextJS. It embeds the public environment variables in the Javascript code generated, your method of changing the IP is correct but its not recommended because in case something wrong happened during the execution the Javascript bundle might break. |
Describe the bug
Fresh deployment of the version v1.9.3 with Docker method.
Error msg:
Failed to connect to the server. Please try again later.
To Reproduce
Steps to reproduce the behavior:
searxng:
ports:
perplexica-backend:
ports:
- 7001:3001
perplexica-frontend:
ports:
- 7000:3000
[MODELS.OLLAMA]
API_URL = "http://10.2.147.70:11434" # Ollama API URL - http://host.docker.internal:11434
[API_ENDPOINTS]
SEARXNG = "http://10.2.147.70:7002" # SearxNG API URL localhost:32768 10.2.147.70:7002
yarn run v1.22.22
�
$ next start
▲ Next.js 14.1.4
✓ Ready in 313ms
5. logs of perplexica-backend
yarn run v1.22.22
$ npm run db:push && node dist/app.js
drizzle-kit: v0.22.7
drizzle-orm: v0.31.2
No config path provided, using default path
Reading config file '/home/perplexica/drizzle.config.ts'
[⣷] Pulling schema from database...
[✓] Pulling schema from database...
[i] No changes detected
info: WebSocket server started on port 7001
info: Server is running on port 7001
The text was updated successfully, but these errors were encountered: