If Iâve understood the entire setup and dependencies of a Nextcloud installation correctly, there are indeed a few key points crucial for a proper installation:
- Proper configuration of NGINX in the file (in my case) /etc/nginx/conf.d/nextcloud.conf (as mentioned above).
Could it be that I need to adjust something in the file /etc/nginx/nginx.conf? Because mine looks like this:
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;
events {
worker_connections 768;
# multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush on;
types_hash_max_size 2048;
# server_tokens off;
# server_names_hash_bucket_size 64;
# server_name_in_redirect off;
include /etc/nginx/mime.types;
default_type application/octet-stream;
##
# SSL Settings
##
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;
##
# Logging Settings
##
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
##
# Gzip Settings
##
gzip on;
# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;
##
# Virtual Host Configs
##
include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;
}
#mail {
# # See sample authentication script at:
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
# # auth_http localhost/auth.php;
# # pop3_capabilities "TOP" "USER";
# # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
# server {
# listen localhost:110;
# protocol pop3;
# proxy on;
# }
#
# server {
# listen localhost:143;
# protocol imap;
# proxy on;
# }
#}
Could it be that the configurations here are conflicting with each other? Because my ânextcloud.confâ is just being included in the ânginx.confâ. Are there any best practices for how to do this most effectively?
- The âconfig.phpâ file of Nextcloud under /var/www/nextcloud/config.
<?php
$CONFIG = array (
'instanceid' => 'XXXX',
'passwordsalt' => 'XXXX',
'secret' => 'XXXX',
'trusted_domains' =>
array (
0 => 'FQSN',
1 => '172.16.90.69',
2 => '172.16.90.8',
3 => '172.16.100.46'
),
'datadirectory' => '/var/www/nextcloud/data',
'dbtype' => 'mysql',
'version' => '28.0.1.1',
'overwrite.cli.url' => 'http://FQSN',
'dbname' => 'nextcloud',
'dbhost' => 'DB-FQSN:3306',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => 'DBUSER',
'dbpassword' => 'DBPASSWORD',
'installed' => true,
'bruteforce.protection.enabled' => 'false',
'brute_force_detection_ban_enabled' => 'false',
);
In the âtrusted domainsâ section, I entered the FQSN (Fully Qualified Subdomain Name) of the Nextcloud, the internal IP address, and the internal IP addresses of the PCs from which I access it (as a test, because I didnât know how else to fix it). I manually changed the DB user and the DB password afterwards. Maybe that was also wrong? I think previously there were hash values there?