Nextcloud AIO using Jailmaker, Dockge, and Nginx Proxy Manager in TrueNAS Scale

[@AinzOoalG0wn]

ur the only person beside stux afaik who covered jailmaker. nicely done.

[@martontichi8611]

when he said "f truecharts" i was like "i liiike him already!!!". i also struggled so much with truecharts

[@JaydenPoland.]

Same here Thanks for the great tutorial, I was able to completely get rid of truecharts

[@mon3628]

not sure why but in my nginx proxy I couldnt use localhost but I needed to use 127.0.0.1

[@satyanarayana9377]

Hi, I'm facing while composing in docker. The error shown at network_mode: host, plz help me.

[@tankuisiong5030]

Thank you so much! Seems like you are the only one who willing to go through all the hassles and shared all these great tutorials to below average Nas user like myself..And your video quality is damn good!!.. I have no idea what to do next after followed capt stux videos..at least now i can get my veri first app into my dockge..thank you so much..!! Do you have plan to make a video tutorial on getting Immich in dockge? How about Traefik?

[@lamgg4]

I'll try to tap into it if I have time but Memories in Nextcloud is very similar to Immich and Traefik is basically Nginx Proxy Manager.

[@lamgg4]

github.com/taiokjk/nextcloud-on-truenas One-stop shop for all the commands in this video (with a bonus cloudflare ddns)

[@JoeMillerG]

Thank you for this tutorial. I am migrating out of truecharts and trying to use the tutorial info for a slightly different setup: domain name managed via Cloudflare -> duckdns domain -> truenas server I'm also trying to point it to an app other than Nextcloud (Airsonic). It's pretty close now. Airsonic runs on its port locally. The certificate is created in NPM. But, it still shows bad gateway when I use the domain name. Any ideas on how to troubleshoot that? Maybe one of the Nextcloud specific settings doesn't work on other apps?

[@drawrb]

Thank you so much for this. Was really struggling with npm but your video finally helped me figure it out

[@lamgg4]

Thanks for the kind words. Glad you got it working. Took me a couple days to figure this out myself haha

[@khoadiep8047]

Bác ơi, e cài nextcloud lên một ổ cứng ssd và lưu file vào 1 ổ cứng hdd khác, khi upload file e thấy nó lưu tạm trên ổ cứng sdd sau đó mới chuyển qua hdd, e gặp tình trạng khi upload file lên nextcloud thì nếu như bị lỗi nó vấn chiếm dung lượng của ổ đĩa ssd, reboot cũng không hết. Bác chỉ em khắc phục với được không ạ, e cảm ơn

[@MrAB5510]

so i cant get nextcloud to submit my domain no matter what i do here. although if i go to my domain i am getting the 502 error. so in my eyes that means the proxy is connected to it correctly but for what ever reason i cant seem to get the AIO to connect at all. any ideas?

[@MrAB5510]

so i figured it out. for what ever reason localhost wasnt working for me in npm. i had to put the actual jailmaker ip in there with the 11000 port. idk why but that worked.

[@lamgg4]

@@MrAB5510 Do you have network_mode: host added to npm? Doing so makes npm to run in the same network as the jail (host), and thus it can access nextcloud using localhost (which nextcloud internal code exposes port 11000 to the jail network)

[@qem888]

At 26:26 you mention you forgot this part about the docker-aio-config, What does this part do? Is it needed? My cloud is working but I don't want to invest too much into it if this part is required for it to work properly. Thank you for the tutorial btw

[@lamgg4]

As said it has to do with some underlying mechanism of how nextcloud-aio handles backups. It needn't (or shouldn't) be changed so you don't have to worry about it.

[@ZoltanHubai]

Thanks for the great tutorial, I was able to completely get rid of truecharts

[@kimbsp]

Well done! Consider to make a video for setting up the included Borgbackup for another drive than the Jailmaker default. My backups ends up in: jailmaker/jails/docker/rootfs/mnt/backup instead of my actual bind-mount.

[@SavannahTL]

Have you been able to get talk to work?

[@loibuitan7909]

em làm theo anh đoạn mà đăng nhập vào nginx proxy manner xong ko đặt lại password giờ làm sao để vào lại trang đó để làm chứng SLL thế anh

[@tankuisiong5030]

I'm stuck..npm stuck at internal error, even though status is showing online. seems like there's an error in letsecrypt, there were some task in challenging and deleting, do you have any idea what should I do next? hope you can help me out here..

[@lamgg4]

Please check the comment chain from @markomilic1813 for the troubleshooting steps. The reason is that either you haven't port forwarded ports 80 and 443, or the ISP has blocked those ports from public, thus Let's Encrypt cannot send the SSL challenge to the nginx' server. You can check the log by going into the npm's container (click the _Bash icon in Dockge) and type "cat /tmp/letsencrypt-log/letsencrypt.log" without the double quotes. I suspect it is status 400, timeout during connect. Also, the host's status in NPM has nothing to do with the SSL certificate. So, it's possible to fail obtaining SSL with status online.

[@tankuisiong5030]

@@lamgg4 Thanks for your reply! before reading your message, i used the manual import ssl method (from google around) by generating the key needed for my domain from cloudflare..then using your instruction above, i saw that certificate is received and stored accordingly..However...the real problem of my entire setup still not able to solve, the moment i change to my domain name in the AIO installation page, it returned error saying that the domain is not reached at port 443. I did the port forwarding in my router, and no firewall blocking anything..just to be sure, i port forward for my container IP address right? Not my truenas IP address correct? since the AIO is accessing based on container static IP:8080... I don't know what to do now....appreciate again if you can point me out any mistakes i could've made..thanks

[@tankuisiong5030]

@@lamgg4 Thanks for your input!! I just checked with my ISP, end up i need to pay for port forwarding..after settle that, now i'm facing issue with the AIO keep giving me error of "Domain does not point to this server or the reverse proxy...."..I triple checked my setup in cloudflare (now pointing to my server address, unproxied), port forwarding 443 to my container IP address, NGINX point to localhost:11000 with valid SSL, restarted the AIO container, restarted npm container...any suggestion? Thanks!

[@tankuisiong5030]

@@lamgg4 I've followed all your steps carefully, even at the step of clicking at the domain name will bring to page with 502 Bad Gateway, and the site is secured accordingly..is it something to do with my router setting now?

[@lamgg4]

@@tankuisiong5030 If you're certain you've configured everything correctly, you can follow this to bypass domain validation: github.com/nextcloud/all-in-one#how-to-skip-the-domain-validation , but I suspect there's issues with your ports still. If you found a solution, please post it here to help others after you 😊

[@NordicDan]

Well I seem to have hit a wall almost immediately After installing and setting the alias for jailmaker, I type in the "jlmkr" command and get "command not found". I did preface it with "sudo" and used my admin password (only clarifying that because I almost forgot to when I first typed it in). Tried the "source" command, going to the dashboard and then back into the shell, and even rebooting the server. No joy. Also went directly into the jailmaker folder, used "dir" to verify it's there, but got the "command not found" response there too. A-yup, I'm stumped.

[@lamgg4]

Can you "cd" into the jailmaker directory and "ls" see if "jlmkr.py" is in there?

[@NordicDan]

@@lamgg4 Yep I had done that, and it does show up. TrueNAS version I'm using is Dragonfish 24.04.2, which makes me wonder if there was a change made in the short amount of time since you made the video that's keeping this from working (though personally I'm sure there's something I'm missing or just doing wrong here). I even tried removing the dataset and starting over with a fresh one while logged in as root, and got the same result.

[@NordicDan]

Replying to my own comment because I finally found the solution: The problem was in the name of my pool. Not sure whether it was the use of spaces or caps (or both), but I changed to a different pool with a single word name with no caps, and it's working perfectly now. I was confident the issue was something on my end, but I'm still very much a novice with Linux based systems so it took a lot of shots in the dark before I found the root (ha pun) of my problem.

[@remcolouter6899]

Awesome tutorial! I got it working. However, I made a mistake with the domain and want to use a different domain now with nextcloud, how can I change the domain, where it says "Submit Domain" afterwards?

[@lamgg4]

Awesome I'm glad it helped! About changing to a new domain, can you follow the steps here and see if it works: github.com/nextcloud/all-in-one#how-to-change-the-domain I've switched to nextcloud (without aio) so it's much simpler with configurations.

[@remcolouter6899]

@@lamgg4 Thanks for the link! Very useful, I will give it a try. I suppose I can always recreate the container and install it again. My previous setup was nextcloud installed on an ubuntu VM running on a QNAP NAS, but it was sooo slow and the setup/configuration was tedious. I am now running proxmox on a Zimacube with TrueNAS virtualized. With your tutorial it was super easy compared to my previous setup. Thanks again!

[@Hunt3rNz]

Hey great tutorial, I'm trying to add external storage using smb on nextcloud. Can't seem to get it to work. getting "insufficient data:no login credentials saved"

[@lamgg4]

@@Hunt3rNz I don't use smb share for my nextcloud but I found this discussion thread on the forum: help.nextcloud.com/t/smb-external-storage-shares-not-mounted-after-some-time-logout-and-login-required/169034/4 Have you tried changing "Log-in credentials" to "Username and password"?

[@ironjustice3067]

Can you show how to do this with truenas scale apps

[@lamgg4]

It was pretty hard configuring using truenas scale apps, thus I switched to using jailmaker to run dockage. It comes with a benefit of running any docker container you want in the future. The setup is pretty simple. I recommend you give it a go!

[@Bigtorstyle]

I was able to complete the whole config and it works pretty well however I am still getting a 502 openresty error that I do not know how to deal with, honestly.

[@elpoyo]

Same for me

[@pzling]

Thanks for this In Truenas scale, how do you know what your network interface is? ('macvlan' in the video)

[@lamgg4]

--network-macvlan is an argument of systemd-nspawn to note that you're connecting using the Ethernet port. You can read more about other types here: manpages.debian.org/bookworm/systemd-container/systemd-nspawn.1.en.html#Networking_Options

[@MuminovicGoran]

Thanks man.

[@jimmyzheng1599]

when i login to nextcloud aio i got problem: Nextcloud AIO v9.2.0 Domaincheck container is not running, i follow your instructions

[@lamgg4]

@@jimmyzheng1599 Can you try this solution? github.com/nextcloud/all-in-one/discussions/4833#discussioncomment-9800965

[@rbode9218]

Gratis tutorial. Can you make additional one; how to migrate the data from a older nextcloud instance (4Tb)

[@markomilic1813]

thanks for this tutorial its great. I did get stuck at the point where I try to SSL certify my HOST but I get an error message saying 'INTERNAL ERROR' after the error it adds the host to my proxy hosts but as a http with a status of Unknown. Any suggestions?

[@lamgg4]

I had the same issue. It's because either of your ports (80 and 443) are not forwarded or blocked by your ISP, so that Let's Encrypt can't ping your server. To troubleshoot, try using any VPN service and access both ports using your.public.ip.here:80 and 443. E.g: 10.150.240.330:80. Accessing port 80 should show you the nginx' Congratulations page, and for port 443 you should see 400 Bad Request. If it's blocked by the ISP, try contacting them to move you to an IP range that doesn't block port 80 or 433. In my case, any IP in the 100.x.x.x range would block port 80 access from outside of my country including Let's Encrypt. I had to restart my router beforehand until I got to the 14.x.x.x range as seen in the video. Cheers.

[@markomilic1813]

@@lamgg4 Thanks for the quick reply. I had a feeling it was something to do with the ports. I definitely ported them. So guess ill try and find out if they are blocked. Thanks!

[@markomilic1813]

@@lamgg4 Just checked, most providers here in Australia use CGNAT which will block you from port forwarding. Need to contact ISP and request to be taken off CGNAT (might cost extra)

[@lamgg4]

@@markomilic1813 Thanks for sharing it here! From what I've read, you should be able to do the same using an IPv6. You only need to change your A DNS record to AAAA and put your IPv6 address there.

[@jhPampoo]

Em cài dùng qua cloudflare tunnel thì vào domain nó cứ ở trang Log in using your Nextcloud AIO passphrase chứ không phải login bằng user với pass để vào dùng Mà hình như dùng qua cloudflare cũng giới hạn nhiều nên chắc cũng không tối ưu anh ha

[@lamgg4]

Nextcloud AIO họ yêu cầu setup trước khi login với username, password nên bạn cần passphrase cho lần đầu tiên cấu hình á. Ở màn hình container Nextcloud AIO trên Dockge, bạn nhấn vào _Bash để log vào container, sau đó gõ lệnh "cat /mnt/docker-aio-config/data/configuration.json" để lấy passphrase trong file config. Passphrase này chỉ dùng khi setup còn sau đó sẽ k sử dụng nữa. Còn Cloudflare thì mình vẫn đang dùng Nextcloud qua domain của Cloudflare nhưng không mở Proxy của họ để chạy được full speed, và hình như họ có policy không dùng proxy cho file streaming với tài khoản free. Mình chỉ Cloudflare như 1 dịch vụ DNS bình thường thôi.

[@jhPampoo]

@@lamgg4 em mới xem lại docs cách setup cho cloudflare tunnel thì chạy được rồi nhưng chậm rì, chắc vì dns nó tạo để dùng tunnel có dùng proxy, tắt proxy đó thì không xài được, dùng tunnel thấy nhiều cái giới hạn quá em làm theo clip anh coi sao :D

[@GenchoGenchev-t5p]

You are doing so much forwarding, but I see you have IPv6 which you have totally neglected. Couldn't you've used that v6 IP to connect to the nextcloud ? Also you haven't show the Overview tab so we could see if it says all checks passed ;)