You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem is with Unraid, I do not have easy access to the root directory of a container. Ultimately I dont think Little Link Custom is going to work on Unraid, since there is no way to do persistent storage, I tried but apparently something goes wrong when it unraid backs up appdata.
You can try to run docker pull julianprieber/littlelink-custom this wont break anything so if this works I could help you setting up your docker image with persitent storage.
Ok so according to the folks at unraid this will not work in unraid, because of the way shares are setup. But they told me to do essentially what I did last night, which was create both the appdata folder, and the docker container without mapping anything. Then copy the files from htdocs, to the appdata folder, rebuild mapping it in such a way.
However for whatever reason, overnight it created all the issues I now have with 404 and 500 errors galore.
They also recommended what would help on unraid, and apparently some other docker solutions; is to put the data that cannot be changed by the issue, maybe it's setup files, or whatever in htdocs, but all of the user data, the database, images, config files, in another folder. For your normal installations it's just a seperate folder alongside htdocs, but allow in the setup for that folder to be mapped elsewhere, and then unraid users could map it to their appdata folder, and everything would work great. If something were to happen to the container itself, they could simply reinstall and point that folder back to appdata and everything would be restored right away.
For now I am going to run it as non persistent and see if I run into any issues that way. Fingers crossed
Activity
JulianPrieber commentedon Mar 7, 2023
On docker?
JulianPrieber commentedon Mar 7, 2023
Behind a reverse proxy or does this also happen when accessing directly over the ip and port?
chrisjameschamp commentedon Mar 7, 2023
Yes it is running on docker, that's a good question let me see if it does it from IP:Port
chrisjameschamp commentedon Mar 7, 2023
Same results if going IP:Port
JulianPrieber commentedon Mar 7, 2023
Could you please turn on debugging in your config and try again?
chrisjameschamp commentedon Mar 7, 2023
Now it wont let me login, I guess I have to restore from backup again, trying to make this persistent is becoming a real pain
chrisjameschamp commentedon Mar 7, 2023
Is there a way to restore from backup?
JulianPrieber commentedon Mar 7, 2023
Not really besides exctarcting the backup file inside the
/(root) directory.chrisjameschamp commentedon Mar 7, 2023
Problem is with Unraid, I do not have easy access to the root directory of a container. Ultimately I dont think Little Link Custom is going to work on Unraid, since there is no way to do persistent storage, I tried but apparently something goes wrong when it unraid backs up appdata.
JulianPrieber commentedon Mar 7, 2023
Can you run docker commands from the Unraid shell?
Something like
docker pull julianprieber/littlelink-customchrisjameschamp commentedon Mar 7, 2023
I believe so
JulianPrieber commentedon Mar 7, 2023
You can try to run
docker pull julianprieber/littlelink-customthis wont break anything so if this works I could help you setting up your docker image with persitent storage.chrisjameschamp commentedon Mar 7, 2023
Yes that works fine, no issues
JulianPrieber commentedon Mar 7, 2023
Alright, what port(s) would you like your docker to run on?
chrisjameschamp commentedon Mar 7, 2023
HTTP Port 2880
HTTPS Port 28443
JulianPrieber commentedon Mar 7, 2023
Please run the commands:
docker volume create llc-unraidand
docker run --detach --name littlelink-custom-unraid --publish 2880:80 --publish 28443:443 --restart unless-stopped --mount source=llc-unraid,target=/htdocs julianprieber/littlelink-customThen your docker should be up and running without any issues.
chrisjameschamp commentedon Mar 7, 2023
Where does it make the llc-unraid volume, is it in the docker img?
JulianPrieber commentedon Mar 7, 2023
Its in one of your folders on your system. Everything inside that folder will persist even if you delete the docker container.
chrisjameschamp commentedon Mar 7, 2023
Ok so according to the folks at unraid this will not work in unraid, because of the way shares are setup. But they told me to do essentially what I did last night, which was create both the appdata folder, and the docker container without mapping anything. Then copy the files from htdocs, to the appdata folder, rebuild mapping it in such a way.
However for whatever reason, overnight it created all the issues I now have with 404 and 500 errors galore.
They also recommended what would help on unraid, and apparently some other docker solutions; is to put the data that cannot be changed by the issue, maybe it's setup files, or whatever in htdocs, but all of the user data, the database, images, config files, in another folder. For your normal installations it's just a seperate folder alongside htdocs, but allow in the setup for that folder to be mapped elsewhere, and then unraid users could map it to their appdata folder, and everything would work great. If something were to happen to the container itself, they could simply reinstall and point that folder back to appdata and everything would be restored right away.
For now I am going to run it as non persistent and see if I run into any issues that way. Fingers crossed
chrisjameschamp commentedon Mar 7, 2023
Also trying to restore files from the backup.zip file causes a 500 error as well