# Multiple Backends on new DietPi Dashboard v0.7.0

**URL:** <https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017>\
**Category:** Troubleshooting\
**Tags:** dietpi-dashboard\
**Created:** [4 March 2026 14:05 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017 "2026-03-04T14:05:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![TomG](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/ac8455/32.png) [@TomG](https://dietpi.com/forum/u/TomG)\
**Post date:** [4 March 2026 14:05 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/1 "2026-03-04T14:05:16Z")

</div>

Hello Guys,

with the last version of DietPi-Dashboard ([v0.6.2](https://github.com/ravenclaw900/DietPi-Dashboard/releases/tag/v0.6.2)) there was a possibility to config several nodes in the GUI by editing the file `config.toml`.

Is this also possible in the new version of DietPi-Dashboard (v0.7.0)?  
And if so, what settings do you have to make in one or both config files?

I tried the `nodes = [“IP-ADDRESS”]`option from the old `config.toml` in the new `config-frontend.toml`file, but that didn’t work.

Any ideas?

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [4 March 2026 14:24 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/2 "2026-03-04T14:24:25Z")

</div>

did you checked our online docs? [System Statistics and Management Options - DietPi.com Docs](https://dietpi.com/docs/software/system_stats/#dietpi-dashboard-multiple-nodes)

---

<div class="post-metadata">

**Author:** ![TomG](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/ac8455/32.png) [@TomG](https://dietpi.com/forum/u/TomG)\
**Post date:** [4 March 2026 15:00 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/3 "2026-03-04T15:00:02Z")

</div>

Hi Joulinar,

maybe I have overlooked this the last time I was searching for it.

Does it work in both directions? Something like that: If I run several DietPi servers headless with DietPi Dashboard, on every server both frontend and backend installed, can I get all the other servers in the `Backend:` pull down list of every frontend in this way? Do I have to put the same secret in all frontend and backend config files to obtain this setup? And can I still use the default backend port (5253) for all nodes or do I have to give every backend its own backend port?

I don’t know if this setting makes any sense to quickly switch from one backend to another, but you have to try it. With the old dashboard it didn’t make much sense, because you had to enter the login password of the new backend when switching and that confused the KeePassXC browser extension or the password storage of the browser. So it was easier to have each DietPi Dashboard in its own browser tab.

I could try it all out for myself, but if someone who knows about it gives a decisive tip, I will get faster to the solution. 🙂

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [4 March 2026 16:18 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/4 "2026-03-04T16:18:47Z")

</div>

I think you’ve misunderstood the principle of frontend/backend.

- Frontend: is the application with the web UI for displaying the data
- Backend: is only the service in the background that collects the data. It cannot display data itself, but sends it to the frontend

In your case, you only need a single system with the frontend installation. All other systems only get the backend. This saves resources, as no frontend is installed as overhead. You connect the individual backend systems to the single frontend.

---

<div class="post-metadata">

**Author:** ![TomG](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/ac8455/32.png) [@TomG](https://dietpi.com/forum/u/TomG)\
**Post date:** [4 March 2026 16:43 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/5 "2026-03-04T16:43:24Z")

</div>

Ok, I understand: This feature is not intended for flexibility, but to save ressources on weaker hardware or virtual machines.  
That makes sense.

I will give it a try!

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [4 March 2026 17:02 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/6 "2026-03-04T17:02:34Z")

</div>

> [@TomG](#):
>
> Ok, I understand: This feature is not intended for flexibility

At least I don’t understand this comment. What do you mean by this? It is still possible to install backend and frontend on every system. But is is not possible to connect one backend to multiple frontends. At least It doesn’t make sense to me.

---

<div class="post-metadata">

**Author:** ![system](https://dietpi.com/forum/uploads/default/original/1X/7e1021de2213860bce185915ce2c1786e56490ec.png) [@system](https://dietpi.com/forum/u/system)\
**Post date:** [2 June 2026 17:03 UTC](https://dietpi.com/forum/t/multiple-backends-on-new-dietpi-dashboard-v0-7-0/25017/7 "2026-06-02T17:03:21Z")

</div>

Closed on 2 June 2026 17:03 UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
