I am trying to set up my nextcloud account so that i can log in. When I try to log in with sudo mount -t davfs2 ... it keeps on asking for my next cloud credentials - it does not get them from the secrets file that i created. I have followed the tutorials online with the only difference being that the tutorials specify to update the /etc/fstab file. But i do not want to do this because i have this set up on my laptop where i only sporadically have access to the internet. I would prefer to use sudo mount.... and have the credential input automaticall from the secrects file (i understand that each time i will need to input my sudo password). I believe that what is happening is that when i use sudo mount .... it is trying to load the system /etc/davfs2 configuration instead of my local .davfs2. I believe this because when i try to configure the /etc/davfs2 (to point to my secrets file) i get config erorrs. But when i purposefully put errors in the local .davfs2 config file the system never seems to recognise it. the only other thing i can think to do is allow local users permission to run mount which i would prefer not to do. What i may be doing wrong? PS - using Xubuntu

A NCP (nextcloudpi) server is stationed at downwind.duckdns.org Safari returns: Chrome returns: A private Safari browser returns the expected NCP webpage. I seek a troubleshooting procedure to diagnose the issue: I am wondering if there is a certificate issue.

I have an issue with a virtual machine running Nextcloud and the version is Ubuntu 22.04 LTS. The system continuously indicates that the logical volume /dev/mapper/ubuntu--vg-ubuntu--lv is full (used 100%). To keep the system running, I’ve had to continuously expand the virtual disk size and extend the logical volume (using this guide ). The logical volume currently has 440GB of size, with 35GB free. Nextcloud storage and a backup disk are mounted in /mnt: Nextcloud storage /mnt/nextcloud is an iSCSI disk on a NAS, currently holding 3TB of data. The backup disk (348 GB) is also mounted in /mnt (/mnt/carpetarespaldosnas).

miusuario@nextcloud:~$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              3.2G  1.7M  3.2G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv  440G  387G   35G  92% /
tmpfs                               16G   28K   16G   1% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
/dev/sda2                          2.0G  254M  1.6G  14% /boot
/dev/sda1                          1.1G  6.1M  1.1G   1% /boot/efi
/dev/sdb1                           24T  3.1T   20T  14% /mnt/nextcloud
tmpfs                              3.2G  4.0K  3.2G   1% /run/user/1000

miusuario@nextcloud:~$ sudo du -cha --max-depth=1 /mnt 2>/dev/null
1.3G    /mnt/NCBACKUP-OLD
1002M   /mnt/NCBACKUP
4.0K    /mnt/ncdata
3.1T    /mnt/nextcloud
349G    /mnt/carpetarespaldosnas
3.5T    /mnt
3.5T    total

Since the logical volume is mounted on /, I tried various ways to get its total size to locate what was using the space, but it doesn’t show more than 30G used.

miusuario@nextcloud:~$ sudo du -cha --max-depth=1 --exclude=/mnt / 2>/dev/null
0       /lib64
28K     /dev
0       /proc
4.5G    /usr
4.0K    /opt
260M    /boot
4.0K    /media
0       /libx32
0       /sbin
0       /lib32
308K    /home
3.8G    /swap.img
1.8G    /snap
124M    /root
1.7M    /run
240K    /tmp
20G     /var
0       /bin
0       /lib
4.0K    /srv
16K     /lost+found
11M     /etc
0       /sys
30G     /
30G     total

So, I have no idea what is filling up the disk or what is actually using the space.

I've installed nextcloud on proxmox in an alpine container using ttecks (rip!) helper script. After some tweaks, I am now able to update nextcloud from the application itself. Now I have the following issue: Nextcloud is still managed by alpines apk, so when I run apk upgrade, the nextcloud package will be updated too, what will break my nextcloud instance. Is there a way to remove (the nextcloud) packages from the management by apk? Like removal of the apk database? I tried to remove it from the /etc/apk/world file. The result is nextcloud beeing removed by apk :/

As per https://help.nextcloud.com/t/how-to-install-an-always-up-to-date-version-of-nextcloud-on-linux/596 I have succesfully run: sudo snap install nextcloud This downloads nextcloud and mounts it. I had expected that after doing this, I would be able to connect to http://localhost. But I get connection refused, so it seems there is a step in which I start the nextcloud service. I have, however, been unable to find that step. What is the next step?

Whenever multiple users are interacting with a Nextcloud installation, there is a possibility of error. Potentially, a family member may delete an old picture or a co-worker might accidentally tick off a task or calendar event, resulting in issues for other users. When full filesystem snapshots or backups of the whole Nextcloud directory are available, they can be used to restore an old state of the entire server. This is fine in case of a complete system crash. However, it becomes an issue if the problem is only noticed after a while and in the mean time, users have modified other data. Then, a choice must be made between rescuing old data and destroying all progress or keeping the current state. The Nextcloud documentation only describes a way to restore the entire installation. Is there a way to more intelligently back up all Nextcloud data automatically (files, messages, calendars, tasks, etc.) so that it can be restored independently? (Maybe even in an online state?)

I am using linux mint and have the nextclound desktop application installed. After each login, I get another login screen: > Authentication required. > The login keyring did not get unlocked when you logged into your computer. Then I can enter my login password again and nextcloud starts without issue. When I open "Passwords" and Keys, Everything looks fine for me: nextcloud is part of the login keyring: How can I configure this, so that the nextcloud can access its keys without me entering the password twice. Edit: I just noticed that if I cancel the "Authentication required" dialog, the keyring is in the locked status:

I have quite basic knowledge regarding my goal. I have both apache2 installed on port 80, and Nextcloud installed on port 82. At the moment I can access "Apache2 Default Page" at 10.1.1.171, and I can access Nextcloud at 10.1.1.171:82. What I would like to do on the home network is enter "nextcloud"or "nextcloud.local", or whatever, into a browser, and be directed to 10.1.1.171:82. I have the following code as a template

ServerName your_domain.com  # Replace with your domain name
    ServerAlias www.your_domain.com

    ProxyPass / http://your_nextcloud_ip:your_nextcloud_port/ 
    ProxyPassReverse / http://your_nextcloud_ip:your_nextcloud_port/ 

    ProxyPreserveHost On
    ProxyPassReverseCookiePath /

    
        Require all granted

and I have modified the easy bits so I now looks like

ServerName your_domain.com  # Replace with your domain name
    ServerAlias www.your_domain.com

    ProxyPass / http://10.1.1.171:82/ 
    ProxyPassReverse / http://10.1.1.171:82/ 

    ProxyPreserveHost On
    ProxyPassReverseCookiePath /

    
        Require all granted

but I can go no further, without help. I don't know what "your_domain.com" should be replaced with given that it is only a local network. I assume that the working code should be placed in /etc/apache2/sites-available and then enabled, but I have been wrong before. Thanks.

I installed Nextcloud v21 via snap on Ubuntu hosted on my VPS. Now I want to enable Pretty URLs to remove the index.php in the URL. Per their documentation , as a prerequisite to editing the Nextcloud config file: > **mod_env** and **mod_rewrite** must be installed on your webserver and the **.htaccess** must be writable by the HTTP user. I am very new at this, but I assume this has to do with the Apache settings. However, given this was a snap install, I'm not sure how I make these adjustments. Can someone please offer some guidance on what I need to do?

I have a newly setup vps at mydomain.com:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.5 LTS
Release:	20.04
Codename:	focal
$

and the administrators installed nextcloud for me. I point my nextcloud clients to work.mydomain.com and it works great. I also want to set up a webserver for www.mydomain.com. Currently, when I point a webbrowser to www.mydomain.com, I get a nextcloud-styled page that says "Access through untrusted domain, Please contact your administrator." This suggests that a webserver is running. Indeed:

$ sudo netstat -tnlp | grep 80
tcp6       0      0 :::80                   :::*                    LISTEN      844835/httpd        
$

and apache2 is not installed. If I install it, I get:

$ service apache2 status
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese>
     Active: failed (Result: exit-code) since Tue 2023-01-31 17:08:54 CET; 1 we>
       Docs: https://httpd.apache.org/docs/2.4/ 
:/$

So, it looks to me like nextcloud's webserver is handling www.mydomain.com. There are only 2 references to the domain in nextcloud's config.php:

...
  'trusted_domains' => 
  array (
    0 => 'work.mydomain.com',
  ),
  'datadirectory' => '/var/snap/nextcloud/common/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '25.0.2.3',
  'overwrite.cli.url' => 'https://work.mydomain.com ',
  ...

So I don't see how calls to www.mydomain.com are being served. How do I serve my own pages to www.mydomain.com?

NexctcloudPi (Raspbian\Debian) was installed on a rpi3 on a USB-SSD. Initial tests were successful. Access via: * duckdns * lets encrypt certificate was successful after initial setup. The system was rebooted and now returns: What Debian commands can be used to probe and test to identify the root cause of the problem? A simple (ELI5) explanation of the error is appreciated: thank you

I operate a Nextcloud server. It is a bunch of docker containers running on Linux. It works as expected for synchronizing files across client machines. However, I would like the server to have easy access to some of the accounts. For example, I use a Nextcloud folder as a simple means of implementing distributed data storage for programs without a builtin synchronization feature. I simply let the program run as if the data is in a local file, but the file just happens to be in a Nextcloud folder, and gets synced across all my machines. It is very convenient and I've used it without issues for years, except that it's hard to run the program on the server itself. The Nextcloud data store is a docker volume and I know that I can find its URL and access the files there. This isn't ideal because: - The path is not very tidy - I'm not sure if the path is stable - I think changing files this way would mess up Nextcloud because the changes would not be tracked in its database - It would probably cause issues should I end up enabling server-side encryption for the account I have also thought about just installing the Nextcloud client on the server. This would probably work but it would double the hard drive space used, which I'd like to avoid as my account is quite large (\~50 GB).

**Setup**: Over the past week I've been trying to set up a Nextcloud Docker instance on an Ubuntu Server VM, in my old 2015 Macbook Pro using VirtualBox and Vagrant. While the VM only has limited storage for the Nextcloud container, the Docker volume responsible for file storage is located in a shared folder provided by VirtualBox, which is located on a 2TB APFS Seagate drive mounted to the MBP, and the procedure is described in the Vagrantfile as follows,

# /vagrant/Vagrantfile
Vagrant.configure("2") do |config|

  config.vm.box = 'ubuntu/focal64'
  config.vm.hostname = 'ubuntu-server'
  config.vm.network # some network configs
  config.vm.synced_folder '/Volumes/SEAGATE/data/nextcloud', '/media/nextcloud'
  config.vm.provision "shell", path: "setup.sh"

end

in the setup.sh as follows,

# /vagrant/setup.sh
sudo apt-get update && sudo apt-get upgrade -y
sudo apt-get -y install docker docker.io docker-compose
sudo docker-compose -f /vagrant/docker-compose.yml up -d

and in the pretty-much-boiler-plate docker-compose.yml as follows,

# /vagrant/docker-compose.yml
version: '3'

services:

  nextcloud_db:
    image: mariadb:10.5
    container_name: nextcloud_db
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - /media/nextcloud/var/lib/mysql:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=
      - MYSQL_PASSWORD=
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  nextcloud:
    image: nextcloud
    container_name: nextcloud_server
    restart: always
    ports:
      - 8080:80
    links:
      - nextcloud_db
    volumes:
      - /media/nextcloud/var/www/html:/var/www/html
    environment:
      - MYSQL_PASSWORD=
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db
      
volumes:
  nextcloud:
  nextcloud_db:

**Note**: when the Vagrant instance finishes, I usually reboot the instance to reload the ownership and groups of the Nextcloud server files. This is because these server files will be assigned to root, when they should be assigned to www-data or systemd-coredump. This incorrect assignment leads to certain directories and files such as /var/www/html/data and config.php being unwritable. *However*, I've encountered an issue that *any* account, despite being allocated unlimited storage and therefore should have at least 1TB storage, has its storage limited to the size of the Vagrant instance, which is often < 50GB. This is because while the account data is correctly located in /var/www/html/data in the Vagrant instance, it is *not* located in the Macbook host in /Volumes/SEAGATE/data/nextcloud/var/www/html/data where it should be. This is despite the fact that on setup, the Nextcloud volume is completely synced on the Seagate drive, which means that at some point after setup the file syncing fails. **To reproduce this**: create the instance with vagrant up, reboot the instance, enter the Nextcloud startup page and create the Nextcloud root user. Data for the root user will only be seen in the guest VM and not in the host machine. **Factors**: This problem occurs on both Windows and MacOS operating systems, and occurs regardless of whether the shared folder is an external mount, or a local directory. For example, switching /Volumes/SEAGATE/data/nextcloud to some local directory ./local/nextcloud will have the same result. Also, switching to Docker bind mounts does not change the outcome. I've tried [moving the Docker data directory](https://www.guguweb.com/2019/02/07/how-to-move-docker-data-directory-to-another-location-on-ubuntu/) , as well as finding ways to move the Docker volumes in general. There are also previous issues that seem related: [External Storage - Folders and Files are not recognized](https://help.nextcloud.com/t/external-storage-folders-and-files-are-not-recognized/147704) It's not that I don't have a solution: if the VM were closed off, there would obviously be no problems, because internal syncs are OK. So, my *nuclear* option right now is to dual boot Ubuntu on the Macbook and install Docker locally to do away with these shenanigans. But that is my last resort. I am more interested in *why* this problem is happening, because I've never encountered a problem before with folders not syncing.

migrate sqlite to mariadb inside a docker image? I installed the docker-compose example from the nextcloud readme (the base version with apache ) but that one still uses sqlite, although there is created a db docker image as well, but it is not used. How do I migrate the sqlite to the created db-docker image? I tried: docker-compose exec --user www-data app php occ db:convert-type --all-apps mysql nextcloud 127.0.0.1 nextcloud which asks for the database password then, but the password I initially set in docker-compose.yml doesn't work

I want to install nextcloud on (Oracle Linux 8 or CentOS 8) from appstream. Is it broken or am I doing something wrong? dnf module enable nextcloud:24 dnf module install nextcloud/default Error: Problem 1: conflicting requests - nothing provides php-pecl-imagick needed by nextcloud-24.0.3-1.module_el8+14920+386fda55.noarch - nothing provides php-pecl-memcached needed by nextcloud-24.0.3-1.module_el8+14920+386fda55.noarch - nothing provides php-pecl-redis5 needed by nextcloud-24.0.3-1.module_el8+14920+386fda55.noarch - nothing provides php-smbclient needed by nextcloud-24.0.3-1.module_el8+14920+386fda55.noarch the same for nextcloud 23.

Enthusiastic home user and perpetual student of Linux (Ubuntu). Got a Raspberry Pi. Until recently, I had FTTC with UK Virgin Media. Was using NAT port forwarding 80 443 to make Pi available on my dynamic IPv4 address. DDNS running on the Pi kept it available regardless of IPv4 address. Pi hosts a snap install of NextCloud on Ubuntu Server 22.04 Raspberry Pi edition. New scenario, FTTP 500/500mbps. IPv6 static addresses, and IPv4 behind CGNAT (what an abomination) so on IPv4, no routing, no inbound connections. DNS updated, AAAA record points at new address. Raspberry Pi available on IPv6 from anywhere with IPv6. UK Virgin Media do not support IPv6. Nor does my cell provider Three UK and many other cell providers. Friends, family, me when I'm at work, can't access due to IPv4 only ISPs. To fix, had a brainwave. Been playing with NginX reverse proxy last month, for other reasons. On my VS hosted by OVH with Ubuntu 22.04, I set up an NginX reverse proxy to a new subdomain, pointing at home subdomain, linking an ipv6 device to ipv4. Server block (NginX config file) as follows, my domain exchanged for example.co.uk

server {
    server_name ip4nc.example.co.uk;
    location / {
        proxy_pass https://nc.example.co.uk ;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/ip4nc.example.co.uk/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/ip4nc.example.co.uk/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
    if ($host = ip4nc.example.co.uk) {
        return 301 https://$host$request_uri ;
    } # managed by Certbot


    listen 80;
    server_name ip4nc.example.co.uk;
    return 404; # managed by Certbot

But now the following: takes ages, absolutely ages, for page to load. When it does, can download nice and fast, but can't upload, looks to work but the NextCloud interface says error as the transfer reaches end-of-file. Have tried adding new domain ip4nc.example.co.uk as trusted to the nextcloud config.php file (you can edit it in the snap) but not tried the IPv4 or v6, might be next thing to try. Any other pointers, greatly appreciated.

> NCSC recommends updating to version 2.15.0 or later, and – where not > possible – mitigating the flaw in Log4j 2.10 and later by setting > system property "log4j2.formatMsgNoLookups" to "true" or removing the > JndiLookup class from the classpath. Source: https://www.zdnet.com/article/log4j-zero-day-flaw-what-you-need-to-know-and-how-to-protect-yourself/ pi@nextcloudpi:~/log4j-detector-master $ uname -a Linux nextcloudpi 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l GNU/Linux Is there a simple terminal command that can retrieve the version of log4j? Tests: === Test for Apache Webserver: https://stackoverflow.com/a/55107891 pi@nextcloudpi:~ $ ps -acx|grep apache 705 ? Ss 0:53 apache2 1600 ? Sl 0:01 apache2 1601 ? Sl 0:01 apache2 unzipped: wget https://github.com/mergebase/log4j-detector/archive/refs/heads/master.zip pi@nextcloudpi:~/log4j-detector-master $ java -jar log4j-detector-2021.12.14.jar [path-to-scan] > hits.txt -bash: java: command not found I am reluctant to install a JDK on the NCP server.

Hello I've recently setup a nextcloud instance with a calendar and wanted to sync my calcurse with it. This is my calcurse-caldav config(password, username and hostname obviously changed):

[General]
Binary = calcurse
Hostname = nextcloud.example.com/nextcloud
Path = remote.php/dav/
AuthMethod = basic
HTTPS = Yes 
DryRun = No  
Verbose = Yes

[Auth]
Username = BestUsername
Password = SuperSecretPassword

I get the following error though:

╰─$ calcurse-caldav --init keep-remote
Connecting to nextcloud.example.com/nextcloud...
Removing all local calcurse objects...
error: The server at nextcloud.example.com/nextcloud replied with HTTP status
error: code 415 (Unsupported Media Type) while trying to access
error: https://nextcloud.example.com/nextcloud/remote.php/dav/ .

I strongly suspect that there is something wrong with my config but I can't understand what as this config worked perfectly with Calibre.

I'm trying to create a nextcloud setup in a debian 10 VM with https and mysql and docker-compose but when I acces https://cloud.example.org my browser says it can't be reached. If I acces the link https://example.org it gives this page : Example Domain This domain is for use in illustrative examples in documents. You may use this domain in literature without prior coordination or asking for permission. This is my docker-compose.yml file version: '3' services: nginx-proxy: image: jwilder/nginx-proxy:alpine labels: - "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy=true" container_name: nextcloud-proxy networks: - nextcloud_network ports: - 80:80 - 443:443 volumes: - /home/dev/nextcloud-data/nginx/vhost.d:/etc/nginx/vhost.d:rw - /home/dev/nextcloud-data/nginx/html:/usr/share/nginx/html:rw - /home/dev/nextcloud-data/nginx/certs:/etc/nginx/certs:ro - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/tmp/docker.sock:ro restart: unless-stopped letsencrypt: image: jrcs/letsencrypt-nginx-proxy-companion container_name: nextcloud-letsencrypt depends_on: - nginx-proxy networks: - nextcloud_network volumes: - /home/dev/nextcloud-data/nginx/vhost.d:/etc/nginx/vhost.d:rw - /home/dev/nextcloud-data/nginx/html:/usr/share/nginx/html:rw - /home/dev/nextcloud-data/nginx/certs:/etc/nginx/certs:rw - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/var/run/docker.sock:ro restart: unless-stopped mysql: image: mariadb container_name: nextcloud-mysql networks: - nextcloud_network volumes: - /home/dev/nextcloud-data/database/mysql:/var/lib/mysql - /etc/localtime:/etc/localtime:ro environment: - MYSQL_ROOT_PASSWORD=mysql_root_testpassword - MYSQL_PASSOWRD=nexcloud_testp@ssw0rd - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud restart: unless-stopped nextcloud-app: image: nextcloud:latest container_name: nextcloud-app networks: - nextcloud_network depends_on: - letsencrypt - nginx-proxy - mysql volumes: - /home/dev/nextcloud-data/data/html:/var/www/html - /home/dev/nextcloud-data/data/config:/var/www/html/config - /home/dev/nextcloud-data/data/data:/var/www/html/data - /home/dev/nextcloud-data/data/themes:/var/www/html/themes - /etc/localtime:/etc/localtime:ro environment: - VIRTUAL_HOST=cloud.example.org - LETSENCRYPT_HOST=cloud.example.org - LETSENCRYPT_EMAIL=root@example.org restart: unless-stopped networks: nextcloud_network: If I run this command : curl -I https://example.org The output is : HTTP/2 200 content-encoding: gzip accept-ranges: bytes age: 427989 cache-control: max-age=604800 content-type: text/html; charset=UTF-8 date: Tue, 21 Sep 2021 18:33:43 GMT etag: "3147526947" expires: Tue, 28 Sep 2021 18:33:43 GMT last-modified: Thu, 17 Oct 2019 07:18:26 GMT server: ECS (dcb/7EEF) x-cache: HIT content-length: 648 For command curl -I https://cloud.example.org The output is : curl: (6) Could not resolve host: cloud.example.org

I recently installed Nextcloud as a snap on a Debian 10 VPS. I want this instance to be served with Apache via a reverse proxy at nextcloud.mysite.com. I have a website being served on ports 80 and 443, so I followed instructions to change my Nextcloud snap's http port to 81 with sudo snap set nextcloud ports.http=81. This allows me to access Nextcloud as expected at nextcloud.mysite.com. However, htop shows me that **multiple php-fpm processes are running, causing my CPU usage to remain constant at around 100%**. Where do these extra processes come from and why does changing the port cause this to happen? I've verified that this only happens when the snap listens on 81 instead of 80. I'm not sure whether the problem is in my Apache site config, the snap instance or something else entirely. # System/package info

$ uname -a
Linux mysite.com 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

$ snap version
snap    2.49.2
snapd   2.49.2
series  16
debian  10
kernel  4.19.0-16-amd64

$ sudo apache2 -v
Server version: Apache/2.4.38 (Debian)
Server built:   2020-08-25T20:08:29

# Apache site config

ServerName mysite.com
ServerAdmin webmaster@localhost
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


	ServerName mysite.com
	ServerAdmin webmaster@localhost
	DocumentRoot /var/www/mysite
	RewriteEngine on
	RewriteCond %{SERVER_NAME} =mysite.com
	RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI}  [END,NE,R=permanent]
	Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
	Header always set X-XSS-Protection "1; mode=block"
	Header always set X-Frame-Options: DENY
	Header always set X-Content-Type-Options: nosniff
	Header always set Content-Security-Policy "[...]"

	Options -Indexes




	ServerName mysite.com
	ServerAlias www.mysite.com
	DocumentRoot /var/www/mysite
	Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
	Header always set X-XSS-Protection "1; mode=block"
	Header always set X-Frame-Options: DENY
	Header always set X-Content-Type-Options: nosniff
	Header always set Content-Security-Policy "[...]"

	Options -Indexes




	ServerName nextcloud.mysite.com
	Redirect Permanent / https://nextcloud.mysite.com 



	ServerName nextcloud.mysite.com
	ProxyRequests Off
	ProxyVia Off
	ProxyPreserveHost On

	Require all granted

	RemoteIPHeader X-Forwarded-For
	RemoteIPTrustedProxy 127.0.0.1
	ProxyPass / http://127.0.0.1:81/ 
	ProxyPassReverse / http://127.0.0.1:81/ 

	Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"


	RewriteEngine on
	RewriteRule ^\.well-known/host-meta /nextcloud/public.php?service=host-meta [QSA,L]
	RewriteRule ^\.well-known/host-meta\.json /nextcloud/public.php?service=host-meta-json [QSA,L]
	RewriteRule ^\.well-known/webfinger /nextcloud/public.php?service=webfinger [QSA,L]
	RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L]
	RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L]	



SSLCertificateFile /etc/letsencrypt/live/mysite.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mysite.com/privkey.pem

# htop