dnielso5

Results 28 comments of dnielso5

urbackup permission error after upgrading to Trixie, unable to run backups

@MichaIng I guess i was wrong, i did get it to point back top my original backups but im getting the same permission error, i tried to apply chown -R...

urbackup permission error after upgrading to Trixie, unable to run backups

@MichaIng ok, hopefully i found the issue. it looks like the tmp file HAS to be located in the main dietpi_userdata folder (/mnt/dietpi_userdata/urbackup/tmp) unless im still missing some kind of...

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

I copied and pasted the entire thing into the console and ran it. This is what it displays at the bottom of my webpage: ** **

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

I restarted the server several times. these are the commands in my history: ``` 482 sudo sed --follow-symlinks -i '/"min-api-version":/d' /etc/docker/daemon.json 483 ## edit, see below! dietpi-software reinstall 185 484...

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

> > In the logs I see no Portainer error/entry anymore after the new version started up, but Nextcloud AIO is in an endless error loop about the `nextcloud-aio-nextcloud` hostname....

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

> Just for clarification, portainer is working but you have issues with some other stacks? So the issue is not with portainer itself but with other containers? im not sure,...

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

@MichaIng so, not sure why this worked but I ran this command: `docker volume rm $(docker volume ls -qf dangling=true)` After that I had to re-pull image and redeploy every...

portainer cant load the container page, stacks that are stopped can no longer restart as "A stack with the name 'xxxx' is already running"

> You removed all volumes. Usually this results in data loss The only issues I seem to see are nextcloud wanting to redo the initial setup, same with wg-easy. Everything...