Closed finalmillenium closed 1 year ago
This issue is usually caused by missing or incomplete python venv installations. You may have had unstable network connection while installing piscsi, or when launching piscsi-web for the first time.
I wrote a section on the wiki for this issue: https://github.com/PiSCSI/piscsi/wiki/Troubleshooting#user-content-Web_Interface
That did indeed fix it. Though the fact that this is happening with the recommended image may still need to be looked at?
I guess one thing we could try is to pre-cache python libraries in the image to bypass the common fail state.
@akuker Is this something that's possible in the image generation script?
I'm going to close this since it's been resolved.
It's not resolved because the same thing just happened to me.
@sqwirral It is resolved in the bleeding-edge development code. We're fixing a few last bugs now in preparation for a stable release. Please bear with us a little longer!
Due to the major changes with the project since my last update, I decided to backup my configs and data, and perform a full re-image. Upon starting up, I configured wifi, localizations, and changed default password. When I attempt to load the web interface, I got the landing page for a long time.
This is the output of
journalctl -f
while attempting to load the config page on a fresh image.I am able to import the python bjoern module in a quick idle session without any errors, and pip shows it properly installed in system level with correct permissions, so I'm scratching my head as to why isn't working. Figured after trying the normal troubleshooting/I'm an idiot stuff before I'd write up an issue.