This should be set to the LAN IP of the system running Docker (not the container IP or public IP). This is used to create /etc/hosts entries within the containers to ensure that NC and CODE connect to each other via the reverse proxy where they will be presented a valid certificate.
If youâre not using Collabora or are using the built-in version, this probably isnât needed.
This was actually the hint that solved my issue. My VPN did block it by configuration and i wasnât aware this was even an option
My wife and me are enjoing the nextcloud setup so much for the last few weeks and really hope this will proof to run solid. Than we can migrate things like the calender into it and we are quite excited.
Thank you very much for this HowTo. Unfortunately the nextcloud does not run as desired. When I start nextcloud for the first time, I get the following error message:
I could solve my problem. After a long, unsuccessful search I started all over again and it worked.
My guess: During the first run of docker-compose up -d I forgot to change the MYSQL_ROOT_PASSWORD in the .env and I think âpasswordâ does not accept MariaDB as password. Is it possible that the repeated call of docker-compose up -d does not re-read the file .env?
Anyway: NextCloud is running! Thanks again @KarlF12 for this helpful HowTo!
You are, at least IMHO, being ungrateful and quite frankly, annoying. @KarlF12 has, what I assume, taken his personal time creating this tutorial, and for people like you to basically jump on his case because of an error with a character, one in which he has already suggested how to fix, is well, annoying.
I could be wrong, but he isnât being paid to do this, and probably has a ârealâ job and responsibilities, and instead of you being appreciative to his work, you are being pedantic.
WOW! What great work you have done with this tutorial. I had been working for days on this before I found it.
EDIT!
I have now deleted quite a few comments because they were due to my own fault. For the help of others I will let this stand as to tell them where I went wrong.
First and gravest mistake: I snap-installed Nextcloud with the Ubuntu server installation. After that I tried to install Collabora Online Docker alongside it. I donât know if it is possible, but for me it created all manner of problems.
Second, since I already had Nextcloud snap installation and Collabora docker I mainly looked for ways to patch or heal my configuration. I tried to redo some things and fix others.
I decided I needed a fresh install of the OS (Ubuntu server without Nextcloud snap). After the fresh install I meticulously followed the above guide and I couldnât be happier! It all works great!
Some things to be careful with:
Read carefully and follow every part of the Docker installation under point 3. There is a link to a guide you need to follow - do it attentively. Same goes for Docker Compose.
Make sure you have port forwarding set to the correct internal ip-address. Mine had changed after reinstallation of OS and I had forgotten to change it in the router settings.
I had a hard time with step 5. Create the folder in /home/username/ and call it nextcloud.
Under step 5.1 (.env-file)
The NEXTCLOUD_IPADDRESS=10.20.30.40 is to be set to internal ip-address of the server.
The passwords I just made up. Is there any other way of doing it?
All those files I created by using âsudo nano /home/username/nextcloud/.envâ and equivalent.
Step 5.4 was unintelligible to me untill I had read it several times. Iâm learning as I am doing. I might need to go through that step soon but so far I havenât.
Step 6.1 - the trusted proxy warning is covered in 6.2.
The apache site configs referred to seems to be the 010-nextcloud.conf found in /etc/apache2/sites-enabled/. Remove the # before the line mentioned in the warning to make the HSTS warning go away.
If you followed the guide closely there should be no problems with step 6.2.
Step 6.4 - in my case at least, the port forwarded as well as the cloud.domain.name:port should be 3478. The guide gives to different ports.
It all works like a charm and I am so happy, happy! Even I could do it
Okay @nightcobe so in regards to the .bashrc stuff, this is just creating a command alias for your Ubuntu user. It shortens the command so you can invoke occ inside the container without having to type âdocker exec -it -u www-data nextcloud phpâ before it every time. Thatâs what you would have to do normally.
There is no need to sudo this part. In fact that will probably make it not work.
Are you able to run Docker commands without sudo? If not then make sure you added your user to the docker group and log out/in.
This is going to be really hard to troubleshoot because I have no idea what state your system is in or what changes youâve already made. If you think the overwriteprotocol https is what broke it then I would start with undoing that and see if it runs.
If not then I think the best thing to do is start a new topic and post your configs so we can take a look.
I donât know why your system wouldnât have a docker group. Iâve never run into that issue. This group is added by the Docker package when itâs installed. Did you follow all the steps in section 3 above?
When running docker-compose itâs best to be in the folder with docker-compose.yml. Otherwise you have to specify the config path every time.
I think that is probably the best course to be honest. Your system has been through a number of other configurations already and I donât know the history to tell you what to look at.
What I can tell you is if you follow my guide above start to finish itâll work. Iâve set up probably 5-10 of them just like this.
I did a fresh restart and clean installed Ubuntu without Nextcloud snap.
After that I followed your guide and everything is working greatâŚ
âŚexcept Talk. Should I follow the install instructions? I didnât. And after setting port forward to port 3478, turnserver:port to cloud.domain.name:3489, adding my coturn secret that I made up earlier (was I supposed to just make it up?) the server test gives me the following error:
Error: no working ICE candidates returned by the TURN server
Should the ports be the same though the guide shows them different?
Thank you! I am so happy right now to have come this far!
/Martin
EDIT:
I changed the port in the nextcloud turn server settings so it reflected the 3478 port on the router port forwarding and the server test gives me OK.
Seems to be working with this configuration.
EDIT2:
I might clean up your post here by removing some of my earlier comments as they came from operating in a broken operating system setup.
I have one last question for you, KarlF12. It might be of interest to others.
It seems like my Nextcloud Docker only uses 195GB out of the 930 GB drive. Is this a common problem? How do I make my Docker configuration understand that there is more space to use?
Would be great if it at least used 700 GB, the rest could be kept for the system/server.
To mount an internal harddrive as part of the Nextcloud configuration, do I need to use what you describe about the extra docker image?