-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
dietpi dashboard Method not allowed #806
Comments
Can you share more details on the SBC used. |
Do you mean what device it's installed on? Sorry, on a PC, under a VMware |
did you probably install the backend only? You would need to install the frontend version. I guess you answered the question regarding the backend with yes. But it would be no 😉 |
Hi @Joulinar, does Dashboard need a graphical interface (XFCE or so) installed on the server? I expected it to work via external web browser |
No
Correct But the dashboard has 2 installation variants. A full version and on the other side only the backend. The backend itself only collects data, but does not display it. For this it needs the full version. See our online docs https://dietpi.com/docs/software/system_stats/#__tabbed_1_5 |
Understood, thanks. Anyway, I don't actually know how to add frontend nodes on the config file. Is that explained somewhere in the docs? |
if you have just one system, install the full version instead of backend. |
Do a reinstall: dietpi-software reinstall 200 And when this question appears:
select |
Describe the bug:
When I try to log in to dietpi dashboard through the ip of dietpi:5252 I am loaded with a white website with the text : Method not allowed
Version of DietPi-Dashboard: I don't know it, I installed it from the dietpi management panel
Nightly or stable: Stable
Version of DietPi: 9.3
Device architecture:
To Reproduce
After installing dietpi I enter through the ip that has dietpi and the port (x.x.x.x:5252) and a blank website comes up with the text Method not allowed
Error log
Additional context
The text was updated successfully, but these errors were encountered: