Nextcloud Docker Stack With A Reverse Proxy Including SSL and DuckDNS

sorry for the delay my wife and i got covered but we are getting better today's video covers installing nexcloud on a reverse proxy the reverse proxy features duck dns along with an auto renewing let's encrypt ssl certificate first we'll create a share for easy access to our app data folder and then we'll collect the information needed to modify the docker components file below finally we'll turn up the stack via command line interface it sounds like a lot but it's really not so let's get to it first thing we need to do is copy our config into notepad and then we're going to fill in the information as we go along so let's head over over to openmediavault so we can get logged in then we're going to go to shared folders under access rights management on the left and then we're just going to create or add a new share and we're going to call it app data the device is going to be our storage array path should populate automatically and just leave the permissions as is and go ahead and click save and then apply at the top and then confirm it now we need to copy the absolute path for our containers so we just mouse over a relative path and click the little down arrow go to columns and an absolute path and we can see our path here and just control p on your keyboard as if you're going to print this screen and then we can copy the path right here and now let's go back over to notepad so now we're going to use the replace feature in our notepad so just hit ctrl h and then in the replace with field we're going to paste our absolute path we just copied and then under where it says find what we're going to copy your absolute path here and make sure there are no spaces at the end of that as well and hit replace all now lines 11 12 25 and 42 should have updated and then while we're in here we need to adjust the maria database password on line 22. back over to open media vault we need to create a user let's go to users under access rights management click on add and then add again we'll name it next cloud give it a password confirm the password and then hit save and then go and apply and then yes to confirm go to smb and sifs on the left under services and then we need to enable smb and then now let's go to shares and hit add and then under the shared folders here our app data folder should be listed we'll just leave everything as default and hit save and now we're going to apply this and confirm it this will share the folder over the lan so we can access it from our windows box it'll make modifying the files later easier outside the command line interface so let's go ahead and test access to our shared folder you open up windows explorer and then the address bar type into backslashes followed by either the server name or the ip address it'll prompt you for the username password and we'll just use the one that we just created for on open media log now let's head over to duckdns.org to collect the last bit of information we need in order to use duck dns's services you have to log into their web page go ahead and use one of the options at the top to get logged in once you're logged in you'll be given a token here and we need to copy this token into our config on the line 40. [Music] be sure there are no spaces or anything like that with it in order for the let's encrypt certificate to redo itself you must enter your email address that you logged into the webpage with online 39 and now back over to dns's web page we need to create a subdomain that we're going to use for next cloud i'm going to type in ss test and now this is sstest.duckdns.org put an add domain there now we can copy this and paste it into our config it will go on line 36 and then if necessary go ahead and adjust the time zones for your containers otherwise we're gonna hit control s to save this file when saving the config file we're going to rename it to docker dash compose dot gamma and then click save and now we need to copy our docker compose file into our app data folder so let's head over to our desktop and grab our file and then back to windows explorer and we should still be in our app data folder and then we'll just paste the file in here we need to forward port 443 in the router to point it to the swag container this process is going to vary depending on your router i use an asus router so here's the web gui for asus here in the asus router you get a wan on the left and then virtual servers and port forwarding at the top and then we're just going to add a profile we'll call it next cloud and the external ports the ssl port 443 we're going to direct this over to our internal server and then we'll enable the port forwarding before we bring up our containers we need to create a new bridge network the newly created bridge network will allow the containers to talk to each other over the host names let's put it into the omv server and then this command here will create a new bridge network named nextcloud if you rename this from anything other than netcloud be sure to update the docker compose config file now that we have our new bridge network let's turn up the containers we need to change directory to the app data folder to the absolute path let's jump back into our config and copy that and then inside the app data folder you can see our docker file now to bring up the containers using docker compose it is just docker dash compose up and then we're going to do a dash d to run it detached back to our app data folder just refresh this and we see we have three new folders that pertain to our containers so we need to modify one of the proxy config files for the swag container so let's just go ahead and go into swag and config then ingenix and then proxy comms and then what we're looking for here is the next cloud sub domain and then i personally make a copy of it first and then we can rename this one i don't like modifying the original in case we need to go back to it for any reason okay and now that we have this renamed we need to restart the swag container so that it will reload this configuration file so let's jump over into portainer and then we'll restart our swag container now let's browse to your duck dns domain using the https protocol be sure to add next cloud to the beginning of your url my example here it's using https and then it's nextcloud.sstest.duckdns.org now we just need to create an admin account and select storage database we're going to select mysql mariadb the username is root the password is whatever you specified in your docker compose file and the database name and hostname both both will be mariadb and this will take some time to finish installing the recommended apps and doing its thing but that's pretty much it if you found this video useful be sure to subscribe and leave a comment to say hi until next time have a great day and thanks for watching

Channel: Steve's Tech Stuff

Views: 11,842

Keywords: docker compose, duckdns, nextcloud tutorial, nextcloud, nextcloud docker, nginx, duckdns docker, docker stack, stevesstuff, install nextcloud, nextcloud container, swag reverse proxy, omv, docker, let's encrypt, nextcloud setup, reverse proxy, nginx reverse proxy, nextcloud hub, ssl, mariadb, openmediavault, cloud storage, ssl certificate, docker container, openmediavault docker

Id: aemqzgNbMPg

Length: 9min 15sec (555 seconds)

Published: Tue Nov 24 2020