-
Notifications
You must be signed in to change notification settings - Fork 10
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
Web UI will not load #182
Comments
@dhaddad355 if you didnt build your own image and used the docker image, could you use the beta image to test the web-ui ? |
@dhaddad355 could you solve the problem? |
@euzu - Yes, I pulled the docker image. Version 2.2.1. I don't see a beta branch, is it? Simple config - Trying to get up and running Config.yml If interested, I could contribute to wiki (I found some documentation confusing to myself) |
@dhaddad355 contirbutions to the documentation are welcome. ghcr.io/euzu/m3u-filter-beta You can see the docker images on the right side of the Browser. |
Same result. Browser console attached. If I break on this line in main.js the UI loads, but as soon as i step into it, it removes everything from the DOM, something strange with authentication; since authentication is disabled
|
you are testing with web_auth disabled ? And what credentials are you using ? |
you did not define any api-proxy user ? how do you want to access the playlists ? Btw i found the problem and will fix it, but without api-proxy.yml you cant access the playlists. |
@dhaddad355 i have pushed a new beta image. The tag is the same, so you need to pull it manually. |
Describe the bug
WebUI fails to load (interface loads, then screen is blank/empty HTML)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Access the web UI
Desktop (please complete the following information):
Additional context
Browser console throws this error:
Failed to load resource: the server responded with a status of 400 (Bad Request) token:1
However, inspecting the network, shows that token is getting a 200; and i see a TOKEN=value cookie set.
The text was updated successfully, but these errors were encountered: