Это видео недоступно.
Сожалеем об этом.
Nextcloud AIO using Jailmaker, Dockge, and Nginx Proxy Manager in TrueNAS Scale
HTML-код
- Опубликовано: 14 авг 2024
- Capt Stux' jailmaker setup video: • TrueNAS Scale: Setting...
Jailmaker's GitHub: github.com/Jip...
Dockge's GitHub: github.com/lou...
Nginx Proxy Manager installation guide: nginxproxymana...
Nextcloud AIO's main GitHub: github.com/nex...
Reverse Proxy Documentation: github.com/nex...
Docker Compose file: github.com/nex...
Nginx Proxy Manager's specific settings: github.com/nex...
Timestamps:
0:00 Intro
0:52 Set up Datasets
2:34 Install Jailmaker
5:37 Jailmaker Startup command
6:48 Create a Docker jail
12:02 Set jail's static IP
14:23 Install Dockge
16:03 Install Nginx Proxy Manager
17:51 Port-forward 80 and 443
19:40 Create a domain
21:28 Set up NPM and SSL
24:18 Set up Nextcloud AIO
when he said "f truecharts" i was like "i liiike him already!!!". i also struggled so much with truecharts
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?
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.
Same here Thanks for the great tutorial, I was able to completely get rid of truecharts
Thank you so much for this. Was really struggling with npm but your video finally helped me figure it out
Thanks for the kind words. Glad you got it working. Took me a couple days to figure this out myself haha
Thanks for the great tutorial, I was able to completely get rid of truecharts
not sure why but in my nginx proxy I couldnt use localhost but I needed to use 127.0.0.1
github.com/taiokjk/nextcloud-on-truenas
One-stop shop for all the commands in this video (with a bonus cloudflare ddns)
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?
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?
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.
@@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)
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.
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"
@@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"?
when i login to nextcloud aio i got problem: Nextcloud AIO v9.2.0 Domaincheck container is not running, i follow your instructions
@@jimmyzheng1599 Can you try this solution? github.com/nextcloud/all-in-one/discussions/4833#discussioncomment-9800965
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
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.
@@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
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 ;)
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..
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.
@@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
@@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!
@@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?
@@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 😊
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?
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.
@@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!
@@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)
@@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.