-
Notifications
You must be signed in to change notification settings - Fork 79
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
Create Account screen doesn't launch #42
Comments
I have a similar problem. My CMD window hangs at 2022-04-18 07:50:48 INFO (SyncWorker_6) [homeassistant.loader] Loaded forked_daapd from homeassistant.components.forked_daapd |
same here.. |
same |
Try latests release |
Found what was causing the issue. Disable AdBlocker. |
For whatever reason it seems to be using a libx265.dll from my inkscape installation, no idea if the issues are related though |
I have the same problem. On new install I do not see the create account screen. I get the screen that Fireball14 shows above. In Firefox pop-ups are not blocked and I do not have any AdBlocker installed. Also tried on Chrome and Edge (same). Running ver 2022.5.3 on Windows 11. Any ideas? |
I have this issue as well, there were no errors during extract/install, have tried all 4 browsers, clearing cache, etc edit: after creating NSSM service and restarting PC it works? probably the restart? |
I just tried launching HassWP_2022.2.3 on my Windows 10 PC but it hangs after launching my default browser. The Home Assistant Login / Create Account screen that I see in YouTube videos showing how to install the program does not appear. My default browser launches, but only thing I see is a blue screen with a logo and Home Assistant displayed. See the attached PDF. I also attached a copy of the CMD script execution window showing what ran after I launched HassWP.cmd.
Can you help me understand what's wrong and how to get HassWP to work? FYI, I'm not an experienced coder so go easy! :-)
HA Screenshot.pdf
HassWP CMD Execution.txt
The text was updated successfully, but these errors were encountered: