This is an oddity while the database is being set up initially. You should be able to carry on creating an account when you see Watches established.
When you create an account the logs may give you some details or errors on your user. However the UI does reflect these errors now. If you are seeing nothing in the logs while trying to crate an account or login, you probably have the wrong API URL. You can test the API is active by navigating to it first. You should see the API is active! message. This is the URL you want to use (Do not include the / at the end, however)
Pruned system and still the same. Reluctant to uninstall docker on my Synology as it says will wipe user data. I donāt have the issue with any other images. Can download ok and use.
Just need to somehow find a way to remove the things that say already exist.
EDIT: I can successfully downgrade to 0.5.5 but nothing higher. No 0.5.6 or latest . Hoping another build (0.5.7) will be downloadable.
This was a fix for multiple architecture support. Glad you could pull the edge image successfully though. Iām going to add alarm support then it will be the latest version
So maybe just the edge tag that allowed me to download as opposed to the commit you made? Does the commit effect the actually pulling of the image or at run point?
Hi,
i also have the problem, that i cannot create the user and connect to the api. I slitly modify your docker-compse to that it fit my needs. Mainly because i use traefik reverse proxy for ssl.
Error message:
Error: Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc. - Check your credentials and try again
Docker logs:
Recreating home-panel-api ... done
Recreating home-panel ... done
Attaching to home-panel-api, home-panel
home-panel-api |
home-panel-api | Copy certs if provided..
home-panel-api | No certificates directory provided
home-panel-api | Run app..
home-panel-api | SSL (HTTPS) is not active. It is advisable to use SSL with Home Panel, especially if the app is exposed to the outside world!
home-panel-api | App is live at http://localhost:3234
home-panel |
home-panel | Copy disabled SSL nginx config
home-panel |
home-panel | Run nginx server..
Maybe you could help me?!
Of course i completly recreated the docker container (delete the running, delete the images and pull it new). Also tried your new edge tag.
Make sure your API URL is set to the IP or hostname of your server. localhost would only be true if you are using the same machine/container that the API is running on. In other words, you need: http://YOUR_IP_OR_HOSTNAME:3234 as your API URL.
I may remove this message since it is causing some confusion
add multiple architecture support (armhf, aarch64, i386 and amd64) (#61)
add support for the alarm component (#65)
allow support for rounded cards (#67)
add military time and date format support (#63)
update docs
The next release will likely be support for the new hass authentication system. I am holding off updating for now while people migrate to the new hass version.
I am having a issue with opening Home Panel with Fully Kiosk Browser. I see the login screen and and are able to login. But I just get a blank screen. I am able to see the screen on the android tablet with Chrome on the same device.