baztardo.snow
Dabbler
- Joined
- May 8, 2020
- Messages
- 38
permission for which?.
for your datasetpermission for which?.
I tried to follow your guide but as of Today and Version: FreeNAS-11.3-U2.1 I get this Error and can't proceed <sigh>
There a lot of this in FreeNas that has changed and make following guide difficult this isn't your fault but FreeNas keeps changing so much stuff it breaks a lot of guides out there it very frustrating...
root@freenas[/mnt/NAS1/steve]# iocage fstab -a nextcloud /mnt/NAS1/cloud /mnt/data nullfs rw 0 0
Destination: /mnt/SSD/iocage/jails/nextcloud/root/mnt/data does not exist or is not a directory.
root@freenas[/mnt/NAS1/steve]#
is There a way to fix this did miss some thing in trying to make it work.. I would greatly appreciate any help ..
iocage exec nextcloud mkdir /mnt/data
iocage fstab -l nextcloud
ok now this is more confusing the guide is to create those mount points from CLI when I got to the mount points under the there aren't any trying to add one ? I should I be adding them here instead of the CLI ?
Well, I have one public IP used for applications and several FQDNs using that IP. What you need is a route for the HTTP request. The server responding on the IP you map in DNS to you domain need to be able to forward or respond to the request. In your case, a browser asking forI have 3 public IP at my disposal and currently using two of them on two on different Router if you missed it I did mention this, I also have FQDN and a DNS set up for it, It has been awhile but I have had all of this working before, this new install of freenas has been giving me problems..
and my Freenas is behind a managed switch x2 10Gb x8 1Gb in on one of the 10Gb connection I mention this also .. that is also connected to a router, The second network has my kids and he Wifi Access point that is behind its own router.
domain.io
will have that resolved to the IP of your router, who in turn forwards 443/80 traffic to your Nextcloud jail IP, the web server in the jail need to listen to that interface and the FQDN, formulate a response and send it back. This works perfectly well with FreeNAS, pfSense and Cloudflare (in my case) so if there are any breaks in the chain in your case, you need to find it. Can the public IP be resolved? Are the ports open? Are the web server configured correctly?Think you may have got the wrong thread @garmWell, I have one public IP used for applications and several FQDNs using that IP. What you need is a route for the HTTP request. The server responding on the IP you map in DNS to you domain need to be able to forward or respond to the request. In your case, a browser asking fordomain.io
will have that resolved to the IP of your router, who in turn forwards 443/80 traffic to your Nextcloud jail IP, the web server in the jail need to listen to that interface and the FQDN, formulate a response and send it back. This works perfectly well with FreeNAS, pfSense and Cloudflare (in my case) so if there are any breaks in the chain in your case, you need to find it. Can the public IP be resolved? Are the ports open? Are the web server configured correctly?
No, that comment is from a 3 year old thread about firewalls in FreeNAS. He is trying to get Nextcloud working, and the bulk of his comments are in this thread, so I think it’s a better fitThink you may have got the wrong thread @garm
were you able to mount your dataset in to the jail?ah its fine at this point I'm pretty disappointed and about to give up..
I've recently been through the process of standing up a NextCloud instance, and found that there were a number of points of difficulty not addressed in the current guides. Specifically, this includes how to properly secure the web server, including proper SSL configuration, php handling and tamper detection. Additionally, I found that many of the current guides on the matter were essentially a list of steps with little to no explanation of what was happening at each stage, so I've put...
It can be either; many of mine give a brief description and then link to the GitHub repo. But I'm not sure why there's an update posted today, and the blog post shows a date a few days ago, when its content still seems to be dealing with Nextcloud 14/15.actual resource not just a link to a blog post.
I'm just preparing for an update. Figured this belongs as a resource given it seems to continue to be useful to a large number of people, and I thought it would be good to take advantage of the "versions" feature provided here to capture the first revision as well as subsequent ones.It can be either; many of mine give a brief description and then link to the GitHub repo. But I'm not sure why there's an update posted today, and the blog post shows a date a few days ago, when its content still seems to be dealing with Nextcloud 14/15.