I have installed last NC 30 on Truenas 24.10 but when I go on the WebUI I got the error:
Access with an untrusted domain
Some can help me considering that with TrueNas I cannot get access and edit the config.php ? I don’t know why…
I can find and go in the Config folder but it doesn’t recognise the nano editor commant…While in the root directory it is recognized…
Thanks Ant
I used the system shell, went to the directory shown in the app information screen (something like /mnt/pool/nextcloud/html) /config/config.php. You may need to su to get into the html directory. The system shell should allow you to use nano to edit the config.
Nextcloud is a PITA, during the initial setup you have to access it from the FQDN that you plan to use during production, otherwise you get the untrusted domain issue.
Can you explain it a bit more? The initial setup through domain.
I’ve also tried to install nextcloud today but it only shows the untrusted domain error page. Tried with all ixVolumes instead of host paths defined by me so basically everything is as stock/default as it can be.
I’ve also tried following this guide (title of this forum’s post, no links allowed:
“A full guide for installing Nextcloud on TrueNAS Scale with Collabora integration and outside access through Nginx Proxy Manager”
but with no luck either.
You need to edit the config file as per Configuration Parameters — Nextcloud latest Administration Manual latest documentation
The “trusted domains” needs to include the address you are going to use to access it (so if you were going to use an ip address such as 192.168.xx.xxx, that needs adding to the trusted domains list.
What I did was to use hostpath to choose specific datasets to use during installation, then shared them via SMB/NFS to my desktop, then found the config file and edited that in notepad. I’ve found iX volumesa to be…challenging. I mention this because for unskilled newbies such as myself, the statement “You may need to su to get into the html directory” and “During initial setup you have to access it from the FQDN” mean zilch.
Unless you actually require most of the features that are available with Nextcloud, I’d highly recommend something much simpler like FileBrowser if you just need access to files and folders, it’s what I switched to after years of fighting with Nextcloud, which has become far too cumbersome IMO.
That being said, here’s the help I can provide. I don’t use it myself anymore, so I can’t really give you a step-by-step guide. Make sure you read the descriptions of the containers on Dockerhub, it will give you a lot of information that can help you. I’m not sure where the sources for the IX containers are pulled/built from, but it’s a good start. Since Docker support is currently in its infancy in SCALE it’s a bit difficult to give exact solutions since I’m pretty much guessing based off of the forms I see when I hit “install”.
Firstly, ensure that you have the NEXTCLOUD_TRUSTED_DOMAIN environmental variable set (not exactly sure if the IX container uses it, but the upstream official container does). This is possibly what is causing your issue since it defines what FQDN (fully qualified domain name) is written to the config file. This FQDN (there can be many) needs to be the same as the FQDN that you initially access Nextcloud from during setup (ex. if you set it as nextcloud.mydomain.com you need to access it via nextcloud.mydomain.com during the initial setup phase)
Sadly it’s not as easy as editing the config file in order to fix this (IIRC) since Nextcloud is a PHP app, which needs to be processed via php-fpm or Apache/Nginx’s PHP module. The AIO version wraps these all together, making the setup process easier. I’m not sure which of the logs are redirected to STDOUT, but it’s a good idea to look at PHP’s error logs and the webserver’s error logs to get more info.
