-
Notifications
You must be signed in to change notification settings - Fork 32
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
cannot connect ui to public-pool api #17
Comments
The API_URL should be a public IP or hostname, not the internal docker host. Your browser needs to be able to reach that API_URL. |
Thanks, fixed it partially with internal IP of the host. But the public-pool-ui still looses connection randomly to the public-pool api It can also be an internal IP address right? public-pool.yourdrvice.ch is the address I am not at home and need to check again later |
the UI is a full client-side (browser) app. So all API calls go from your browser directly to the public-pool API. You need open the API port to the world and use the public IP (or hostname) so your browser can make the API calls. You can see if it works by opening the Network tab of your browsers dev tools, and inspect the requests to e.g. "<api_url>/network". It should respond with some network info JSON. |
Yes i made it to work and of course the API port is opened to the WAN. It worked this morning, now checked again on your pool and the public-pool-ui doesnt get any infos anymore from the API of the public-pool Backend Need to See this evening what is going on |
the title states the problem.
Everything runs on the same system. Public-pool runs fine and is already connected with my bitaxe
But ui doesnt seem to get a connection to the public-pool
my .env of public pool:
my enviroment.prod.ts:
my docker-compose-yml of the public pool:
the docker command I am using to setup public-pool-ui:
docker run --name public-pool-ui -d -p 8081:80 -e DOMAIN=public-pool.yourdevice.ch public-pool-ui
any idea? the docker logs of the public-ui continer doesnt show any useful informations
The text was updated successfully, but these errors were encountered: