danb35 / freenas-iocage-nextcloud

Script to create an iocage jail on FreeNAS for the latest Nextcloud 28 release, including Caddy, MariaDB or PostgreSQL, and Let's Encrypt
GNU General Public License v3.0
258 stars 70 forks source link

Cant Install #170

Closed jasegw closed 3 years ago

jasegw commented 3 years ago

Fresh install of FreeNAS and/or TruNAS, as I have tried both. Here is the error.

`===== Message from php74-pdo_mysql-7.4.18:

-- This file has been added to automatically load the installed extension: /usr/local/etc/php/ext-30-pdo_mysql.ini

Message from php74-mysqli-7.4.18:

-- This file has been added to automatically load the installed extension: /usr/local/etc/php/ext-20-mysqli.ini /bin/sh: go: not found Command: /bin/sh -c go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest failed! Failed to get xcaddy, terminating.`

danb35 commented 3 years ago

I can't duplicate this, and it would mean that go didn't install, which should have terminated the jail creation. Do you have any of the earlier output of the script? It should look like this:

root@freenas[/mnt/tank/freenas-iocage-nextcloud]# ./nextcloud-jail.sh
JAIL_INTERFACES not set, defaulting to: vnet0:bridge0
ls: /mnt/tank/nextcloud/config: No such file or directory
nextcloud successfully created!

Testing Host DNS response to pkg.freebsd.org
Testing nextcloud's SRV response to pkg.freebsd.org
Testing nextcloud's DNSSEC response to pkg.freebsd.org

Installing pkg...
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.

Installing supplied packages:
  - nano...
  - sudo...
  - redis...

[snip]

[1] https://dev.gnupg.org/rGecfc4db3a2f8bc2652ba4ac4de5ca1cd13bfcbec
  - bash...
  - go...
  - git...
jasegw commented 3 years ago

Hi

It fails immediately after creating the jail, to overcome that, I commented out the jail creation as it’s already done it, enable NAT within the jail to get where it is now.

On Fri, 7 May 2021 at 12:33, danb35 @.***> wrote:

I can't duplicate this, and it would mean that go didn't install, which should have terminated the jail creation. Do you have any of the earlier output of the script? It should look like this:

@.***[/mnt/tank/freenas-iocage-nextcloud]# ./nextcloud-jail.sh JAIL_INTERFACES not set, defaulting to: vnet0:bridge0 ls: /mnt/tank/nextcloud/config: No such file or directory nextcloud successfully created!

Testing Host DNS response to pkg.freebsd.org Testing nextcloud's SRV response to pkg.freebsd.org Testing nextcloud's DNSSEC response to pkg.freebsd.org

Installing pkg... You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.

Installing supplied packages:

  • nano...
  • sudo...
  • redis...

[snip]

[1] https://dev.gnupg.org/rGecfc4db3a2f8bc2652ba4ac4de5ca1cd13bfcbec

  • bash...
  • go...
  • git...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/170#issuecomment-834291546, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJ347BHERAPZA6AUPST4ODTMPFZBANCNFSM44JKP76A .

-- .: Sent via Airmail :.

danb35 commented 3 years ago

It fails immediately after creating the jail, to overcome that, I commented out the jail creation as it’s already done it

What do you mean by "it's already done it"? You've already created the jail (e.g, through the GUI)? That wouldn't be expected to work; the step of creating the jail installs a bunch of software dependencies that you'd be missing (including go, which is the cause of the immediate problem you're reporting).

And in what way does it fail immediately after creating the jail?

jasegw commented 3 years ago

Your script creates the jail, then fails as it can’t access the outside world until I enable NAT within the jail. When I run again, it fails saying jail already there, hence I disable that bit.

On Fri, 7 May 2021 at 12:49, danb35 @.***> wrote:

It fails immediately after creating the jail, to overcome that, I commented out the jail creation as it’s already done it

What do you mean by "it's already done it"? You've already created the jail (e.g, through the GUI)? That wouldn't be expected to work; the step of creating the jail installs a bunch of software dependencies that you'd be missing (including go, which is the cause of the immediate problem you're reporting).

And in what way does it fail immediately after creating the jail?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/170#issuecomment-834302591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJ347GOTFHX4VBDP3PYDW3TMPHVFANCNFSM44JKP76A .

-- .: Sent via Airmail :.

jasegw commented 3 years ago

I can do a screen video, on a fresh install if that helps. One of the biggest issues I think for me, is it does not enable NAT within the jail, so fails trying to reach freebsd.

On Fri, 7 May 2021 at 12:49, danb35 @.***> wrote:

It fails immediately after creating the jail, to overcome that, I commented out the jail creation as it’s already done it

What do you mean by "it's already done it"? You've already created the jail (e.g, through the GUI)? That wouldn't be expected to work; the step of creating the jail installs a bunch of software dependencies that you'd be missing (including go, which is the cause of the immediate problem you're reporting).

And in what way does it fail immediately after creating the jail?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/170#issuecomment-834302591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJ347GOTFHX4VBDP3PYDW3TMPHVFANCNFSM44JKP76A .

-- .: Sent via Airmail :.

danb35 commented 3 years ago

It should not enable NAT within the jail. Why do you think you need NAT enabled?

jasegw commented 3 years ago

That’s the only way i can get it to communicate with the outside world.

On Fri, 7 May 2021 at 14:19, danb35 @.***> wrote:

It should not enable NAT within the jail. Why do you think you need NAT enabled?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/danb35/freenas-iocage-nextcloud/issues/170#issuecomment-834378599, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQJ347AYBT3ACJLKQTPWA3DTMPSHVANCNFSM44JKP76A .

-- .: Sent via Airmail :.

danb35 commented 3 years ago

Then that's what needs to be fixed. The installation created by this script isn't designed to work behind NAT, even if it could complete (which it could, if you'd installed all the packages inside it). The problem isn't with this script; it's something in your NAS network configuration. Suggest following up on the forum.