How to install Nextcloud 13 in FreeNAS with all checks passed updated to use iocage

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504

spotcatbug

Dabbler
Joined
Nov 6, 2017
Messages
43
Use the --force-renew (or maybe --force-renewal) flag to certbot.

Yup. Worked. Thanks.

Now I just need to get the memory cache going.
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
Try creating the iocage jail with vnet like :
Code:
iocage create -n nextcloud -r 11.1-RELEASE ip4_addr="vnet0|192.168.1.11/24" defaultrouter="192.168.1.2" vnet="on" allow_raw_sockets="1" boot="on"

Change the IP address and default router to match your setup.

Thanks !!!!!!!!!!!!!!!!!!!!!!! Everything works great !! Just installing everything now (: (:
 

jeremygb

Cadet
Joined
Apr 4, 2018
Messages
4
Only through the new GUI, not in the old GUI.

You're running into the same problem I was seeing; @TimvH found the fix:
Code:
cd /tmp
git clone --recursive https://github.com/iocage/iocage
cp -R iocage/iocage/lib/ /usr/local/lib/python3.6/site-packages/iocage/lib



I ran that code and it seems like it did what is supposed to do, but there was no change in the outcome when I attempt to start the jail.
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
I was able to install but there are some problems I encountered.

I could not set the SSL (https)
As I execute the command
certbot certonly -webroroot -w / usr / local / www / apache24 / data / nextcloud -d YOURSITE.COM (with my domain of course) so he tells me this error:

Code:
Domain: My Domain
   Type: unauthorized
   Detail: Invalid response from
   http: // my domain / .well-known / acme-challenge / X6sE7P8JRJ6Goen0FHOHS1DmRLb2tUFCcouRafFDz80:
       ">"<! DOCTYPE HTML PUBLIC" - // IETF // DTD HTML 2.0 // EN ">
       "><html> <head>
   404 Not Found    "><title> 404 Not Found </ title>
       "></ head> <body>
   Not Found    "><h1> Not Found </ h1>
   <p "

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A / AAAA record (s) for that domain
   contain (s) the right IP address.

And that I am trying the same command with the IP of the Jail:

Code:
Requested name  IP of the Jail is an IP address. The Let's Encrypt certificate authority will not issue certificates for a bare IP address.


And I noticed that if I try to connect through my domain then I still have access through HTTP even though I have done what was written in the guide to redirect the media to HTTPS.
And with I try to get in through the IP of the jail then he straightens me up to HTTPS even before I did what was written in the guide I think this was called right after I installed the nextcloud. In the end I was able to through the Edge browser on HTTP but from nowhere else he did not want to connect via HTTP

And I try to log in through the HTTPS browser (in any browser) then this error appears:

Secure Connection Failed

An error occurred during a connection to my domain / IP of the prison. SSL received a record that exceeded the maximum permitted length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG


And now for another problem.

I want and have to use SMB storage because of permissions problems that we will not go into it now but the problem is that after I run the external storage in nextcloud he writes me this error:
Code:
The FTP support in PHP is not enabled or installed. Mounting of "FTP" is not possible. Please ask your system administrator to install it.
"smbclient" is not installed. Installing of "SMB / CIFS", "SMB / CIFS using OC login" is not possible. Please ask your system administrator to install it.


I use the dynamic DNS of duckdns and there everything is set correctly I've used this domain previously and everything worked so you can rule out a problem with it

I have no idea what exactly to install or run and you should fix it!

please! Help me fix these problems / errors

Thank you (:
Itay
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
certbot certonly -webroroot -w / usr / local / www / apache24 / data / nextcloud -d YOURSITE.COM
Why do you have all the spaces in the webroot path? It should be /usr/local/www/apache24/data/nextcloud, all together with no spaces.
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
Why do you have all the spaces in the webroot path? It should be /usr/local/www/apache24/data/nextcloud, all together with no spaces.
It was without spaces it probably because Google Translation did it (I did not notice when I translated)
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
So you ran the command without spaces in the path? So much for the easy answer then. OK, try a manual test. First, create the challenge directory: mkdir -p /usr/local/www/apache24/data/nextcloud/.well-known/acme-challenge. Then, create a text file there: nano /usr/local/www/apache24/data/nextcloud/.well-known/acme-challenge/test.txt. Put a line or two of text in that file and save it. Then, from outside your LAN (perhaps from work, or turn off wifi on your smartphone and try from there), try to browse to http://yourdomain/.well-known/acme-challenge/test.txt.
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
So you ran the command without spaces in the path? So much for the easy answer then. OK, try a manual test. First, create the challenge directory: mkdir -p /usr/local/www/apache24/data/nextcloud/.well-known/acme-challenge. Then, create a text file there: nano /usr/local/www/apache24/data/nextcloud/.well-known/acme-challenge/test.txt. Put a line or two of text in that file and save it. Then, from outside your LAN (perhaps from work, or turn off wifi on your smartphone and try from there), try to browse to http://yourdomain/.well-known/acme-challenge/test.txt.

Ok it worked I saw what I wrote under http://mydomain/nextcloud/.well-known/acme-challenge/test.txt
How do we go from here?
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
Sounds like you need to remove /nextcloud from your webroot path.

Will this solve my problems with the creation of SSL (HTTPS)?

Or one of the other issues I mentioned above?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Will this solve my problems with the creation of SSL (HTTPS)?
Removing /nextcloud from the webroot path in the certbot command should allow you to obtain your cert.
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
Removing /nextcloud from the webroot path in the certbot command should allow you to obtain your cert.
Ok let's try.
What command to do it?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
The same command you used before, but without /nextcloud at the end of the webroot path.

This is the command I used:
certbot certonly --webroot -w /usr/local/www/apache24/data/nextcloud -d YOURSITE.COM with my domain

And now to do just that?
certbot certonly --webroot -w /usr/local/www/apache24/data -d YOURSITE.COM with my domain
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
The same command you used before, but without /nextcloud at the end of the webroot path.


This is the command I used:
certbot certonly --webroot -w /usr/local/www/apache24/data/nextcloud -d YOURSITE.COM with my domain

And now to do just that?
certbot certonly --webroot -w /usr/local/www/apache24/data -d YOURSITE.COM with my domain
?????????
 

Itay1778

Patron
Joined
Jan 29, 2018
Messages
269
Top