-
[Support] Djoss - HandBrake
Hi, any update on 1.6.(1)? I've pretty much switched to AV1 encoding now but I'm having to use my windows pc which isn't ideal as my pc isn't on long enough to do most of my encodes. Many thanks!
-
Tango started following New smart switch for home , UPS Choice - APC SmartConnect and Webshop selling server chassis
-
[Support] GitLab-CE
Thanks @opticon that indeed work at getting me pass that error, unfortunately it was then failing on another problem: I managed to fix this myself by changing ownership (recursively) of the authorized_keys directory to user/group 998. chown -R 998:998 .ssh For anyone else who has this problem I think it was down to me running the "New Permissions" tool on the appdata share which I know is not recommended, but I was fixing another access permission problem at the time back just before christmas. The container is now starting fine, just hope I wont get any further issues. Lessons learnt i guess. [EDIT] Wow it seems I really did mess things up, gitlab started and all the project where there but it said there was no code repositories available in each project, I shortly needed a new pair of underwear. I've tried to change (recursive) ownership of the git-data directory as well but after restart gitlab still doesn't want to see whats inside the repositories directory. I guess if I can't fix this I might have to start the gitlab container from scratch, and see if I have a copy of all my repositories somewhere.
-
[Support] GitLab-CE
Hi, I've booted up my container that I have not used since before Christmas and it won't start, previously it was running fine. It looks like its failing when chef is building the environment, I found this in the '/appdata/gitlab-ce/log/reconfigure' log file: Note: None of the other log directories have 2018 date logs. Anyone got any idea what the problem might be? I don't know if this is related to the 6.4.x upgrade that I did last week. Previously I was on 6.3.5.
-
[Support] Linuxserver.io - Duplicati
Has anyone setup Duplicati to connect to a Minio docker (s3 compatible backend) via the letsencrypt docker? I've attempted to set this up, hitting mino via https in a browser works fine, no errors, but when I try and point Duplicati at it i get the following error: Failed to connect: The request signature we calculated does not match the signature you provided. Check your key and signing method. Pointing Duplicati directly at the mino docker via non ssl works fine. Wasn't sure which docker container thread i should be asking this in but any help would be appreciated.
Tango
Members
-
Joined
-
Last visited