[BUG] 2.1.1 broke updates

[yuriw]

trafficstars

Environment

Self-Hosted (Bare Metal)

System

Debian 12

Version

2.1.2

Describe the problem

See details here https://github.com/Lissy93/dashy/discussions/1511 and here https://github.com/tteck/Proxmox/discussions/2631

Additional info

No response

Please tick the boxes

• [X] You have explained the issue clearly, and included all relevant info
• [X] You are using a supported version of Dashy
• [X] You've checked that this issue hasn't already been raised
• [X] You've checked the docs and troubleshooting guide
• [X] You agree to the code of conduct

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[CrazyWolf13]

Hi Yeah I do know that tteck reverted the lxc version, however this is NOT maintained by Lissy or in any way related to dashy. He just provides an installation script.

Once we have ironed out all the small bugs I will inform him, so he can switch back to the new version.

In the meantime, due to his config dir change it's probably best to create an issue at his repository as that is a problem with his script and not with dashy.

Regarding your request to the config copy, in the proxmox web-gui you can see the lxc id, then you can open a shell on the host proxmox and enter: pct enter {id} then you will get a shell from the dashy lxc.

There you can navigate to the folder where dashy is stored, print out conf.yml with cat: cat conf.yml and paste it into the new conf.yml on the new host, by editing with nano: sudo nano conf.yml you could also copy the file to the new lxc.

If you have anymore questions feel free to reply.

[p6002]

When will the bug be fixed?

[CrazyWolf13]

@p6002 I'm unsure what the realtion between the original post of this issue and your problem is.

Please share a bit more details, otherwise it's quite impossible to diagnose. Are you sure you have set the correct read and write permissions? Has it worked before and now not anymore or is this your first time trying ?

[p6002]

I thought it concerned the latest update, which is why I wrote here. The dashboard stopped working a few days ago, but now I only have time to diagnose it. I didn't do anything custom, it is my homepage in the browser. I've been using dashboard for a year, it's on a special vm with important stuff that I don't touch until it breaks. It is possible that watchtower updated something automatically?

[CrazyWolf13]

I thought it concerned the latest update, which is why I wrote here. The dashboard stopped working a few days ago, but now I only have time to diagnose it. I didn't do anything custom, it is my homepage in the browser. I've been using dashboard for a year, it's on a special vm with important stuff that I don't touch until it breaks. It is possible that watchtower updated something automatically?

This issue is regarding an external script on tteck for proxmox, please create a new issue with your details.

[Lissy93]

Once we have ironed out all the small bugs I will inform him, so he can switch back to the new version.

@CrazyWolf13 I don't know too much about Proxmox, but I would think that the 3.0.0 should be good to go / unpin from 2.1.1?

[CrazyWolf13]

@Lissy93 thank you for reminding, already had that on the radar as well, i will notify tteck about the changes. Yeah definitely is good to go, basically proxmox lxc creator by tteck is just an automated deploy for install from source within I think debian 12.

Edit: Oh you've already posted into the discussion, great! https://github.com/tteck/Proxmox/discussions/2631#discussioncomment-9182056

[CrazyWolf13]

Think this has been resolved.