JorgeB Posted Wednesday at 10:43 AM Share Posted Wednesday at 10:43 AM You can restore the bare minimum from the backup, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder, if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit. 1 Quote Link to comment
JorgeB Posted Wednesday at 10:43 AM Share Posted Wednesday at 10:43 AM Also, if the containers that you are using are from LinuxServer (lsio), edit the containers and in the Repository Setting (may need to switch to advanced view at the top right), remove the lscr.io/ from the entry. IE: It would likely be akin to "lscr.io/linuxserver/container_name". Change it to be "linuxserver/container_name" and see if the problem continues. Quote Link to comment
RichardIstSauer Posted Wednesday at 10:54 AM Author Share Posted Wednesday at 10:54 AM 9 minutes ago, JorgeB said: Also, if the containers that you are using are from LinuxServer (lsio), edit the containers and in the Repository Setting (may need to switch to advanced view at the top right), remove the lscr.io/ from the entry. IE: It would likely be akin to "lscr.io/linuxserver/container_name". Change it to be "linuxserver/container_name" and see if the problem continues. I have some from LinuxServer, but all containers start with linuxserver/. And I have some from GitHub Packages they all start with ghcr.io/. Would it be wrong when it starts with lscr.io/linuxserver/? Quote Link to comment
JorgeB Posted Wednesday at 10:56 AM Share Posted Wednesday at 10:56 AM 1 minute ago, RichardIstSauer said: ghcr.io/ Not sure about these. 1 minute ago, RichardIstSauer said: lscr.io/linuxserver/? These have been known to cause issues. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.