Infinite Loading Issue After Following Docker Installation Tutorial

[kingdomad]

Describe the bug
After following the tutorial steps to start the application using Docker, the page keeps loading indefinitely.

To Reproduce
Steps to reproduce the behavior:

1. Follow the tutorial to start the application using Docker.
2. Access the application’s webpage as instructed in the tutorial.
3. Observe that the page keeps loading without any content.

Expected behavior
I expected the page to load normally and display the application content.

Screenshots

[atomicangel]

I just updated the docker containers on my system and that is when the issue started for me as well. I double checked my configuration (I'm not using a .env file that I can see if that matters.) in the docker-compose.yaml and it looks like it wasn't modified since I last restarted the containers. I then tried git pull on the local folder and it made some changes and the issue persists.

I also made sure my ollama instance was up to date as well, to eliminate that as a source of trouble.

[kingdomad]

Edit the docker-compose.yaml and change the 127.0.0.1 in the args to the server's IP address:

perplexica-frontend:
    build:
      context: .
      dockerfile: app.dockerfile
      args:
        - NEXT_PUBLIC_API_URL=http://127.0.0.1:3001/api
        - NEXT_PUBLIC_WS_URL=ws://127.0.0.1:3001

This way, it will run successfully.

[atomicangel]

I have done that, issue persists. I did that when I had configured it originally so I could access it via a reverse proxy. This is not resolved. I also cannot access it via it's internal address either, and if the settings mentioned matters, then that would explain that but it does not explain why the reverse proxy does not work.On Nov 15, 2024 9:21 PM, kingdomad ***@***.***> wrote: Edit the docker-compose.yaml and change the 127.0.0.1 in the args to the server's IP address: perplexica-frontend: build: context: . dockerfile: app.dockerfile args: - NEXT_PUBLIC_API_URL=http://127.0.0.1:3001/api - NEXT_PUBLIC_WS_URL=ws://127.0.0.1:3001 This way, it will run successfully. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[nanhoes]

same issue