Everything posted by andreidelait
-
[Support] Data-Monkey - netdata
It works now. Thank You.
-
[Support] Data-Monkey - netdata
Removed everything (container, images, folder from appdata, docker template). Installed it again and the same: no docker no VMs are shown.
-
[Support] Data-Monkey - netdata
After switching from the old repo to the official one, the docker containers are not shown in Netdada. Is there something else that I need to configure?
-
[Support] Linuxserver.io - Nextcloud
I cannot connect to the onlyoffice server for some reason. When I press Save after I add the URL for it I get this error: Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) I used spaceinvader tutorial to configure it.
-
[Support] Linuxserver.io - Nextcloud
Yes
-
[Support] Linuxserver.io - Nextcloud
I use local as well and never had a problem. I don't see any reason to use SMB unless you have to mount a share from a different host. Why bother with a different protocol when you already have the files stored on the same machine?
-
[Support] Linuxserver.io - Nextcloud
www2.conf Here is what I have configured in that file. Please do your research about each parameter. That way you will set the correct values for you. pm = ondemand pm.max_children = 300 pm.start_servers = 8 pm.min_spare_servers = 8 pm.max_spare_servers = 16 pm.max_requests = 500
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
OMG, I had to change the theme to see it. I'm colorblind and I didn't see it on that theme. Thank You.
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
-
Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array
How do I remove a remote SMB Share from UD? Sorry if the answer is here somwhere but I couldn't find it yet.
-
[Support] knex666 - Nextcloud
The only vulnerability is __Host-Prefix So I gen an A.
-
[Support] knex666 - Nextcloud
I'm trying to reverse proxy using letsencrypt docker but in the Settings/Overview section I get this error: The "Referrer-Policy" HTTP header is not set to "no-referrer", "no-referrer-when-downgrade", "strict-origin", "strict-origin-when-cross-origin" or "same-origin" I have this set to but for some reason I still get the error. Does anybody else have this issue?
-
[Support] Linuxserver.io - Nextcloud
Thank you for making this clear. I was poking trough the files to trace the issue and compare both containers. So I will install the onlyoffice container in this case.
-
[Support] Linuxserver.io - Nextcloud
I'm not so sure about this. I've installed the official docker using the latest tag and onlyoffice works out of the box on that one.
-
[Support] Linuxserver.io - Nextcloud
Yes in that one.
-
[Support] Linuxserver.io - Nextcloud
FOUND THE SOLUTION for 504 error In the letsencrypt config for nextcloud you need to add location / { ........ proxy_read_timeout 3600; ........ } I have 3600 for testing purposes. You have to adjust that as you need. By default is 60 somwhere in nginx backend and thats why you get the 504 error after 1 min.
-
[Support] Linuxserver.io - Nextcloud
If you are using Mariadb that means you have a different docker cntainer for that. You have to migrate that one aswell.
-
[Support] Linuxserver.io - Nextcloud
In your nextcloud config folder, usually /mnt/user/appdata/nextcloud/nginx/site-confs/ should be a file named default Edit that file.
-
Docker high image disk utilization: why is my docker image/disk getting full?
du command goes across filesystem for sure I've tried this one too and mine returns a 74G /var/lib/docker/btrfs, my docker image having 40G. However if I insert -x argument it returns 0 for that volume. I'm sure it calculates some volume mappings or something. So usually I use root@Tower:~# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 28 28 11.57GB 784.9MB (6%) Containers 28 16 1.744GB 372.3MB (21%) Local Volumes 11 1 39.68MB 0B (0%) Build Cache 0 0 0B 0B or root@Tower:~# df -h | grep /dev/loop2 /dev/loop2 40G 15G 25G 38% /var/lib/docker
-
[Support] Linuxserver.io - Nextcloud
I quit troubleshooting this error a few weeks ago but now you got me interested again. I already tried this but here is where I'm stuck now. If I access my nexcloud instance locally by IP address it works fine. If I access it vie letsencrypt reverse proxy I still get the 504 error on large files. So now I will try to defeat letsencrypt config in this regard and I'll come back if I win. Please let me know if you are using letsencrypt and it works for you. Thank You.
-
[Support] Linuxserver.io - Nextcloud
Yes that is it and also I think there is one more called overwritehost You close a comment section with */ I don't think it works with that \ in there.
-
[Support] Linuxserver.io - Nextcloud
You need to edit config.php and comment the redirect part in order to access it via IP address. After you're done troubleshooting you uncomment the redirect and that's it.
-
VM Backup Plugin
Hi, Maybe I don't understand how snapshots work. I understand you need QEMU Guest Agent in order to be able to create snapshots. So I tried with a Windows 10 VM and it creates a snap file but also create a full vdisk copy in backup directory. Every backup it creates another full disk image. Is that how it works or I'm doing it wrong. I tought that a snapshot saves just the data that's different from the latest vdisk.
-
[Support] Linuxserver.io - Nextcloud
For now that's the only backup I have but it's set weekly and it stops the containers to do it. I will consider BTRFS snapshots in the future but I have to do some research about it, as for now I'm not familiar with that.
-
[Support] Linuxserver.io - Nextcloud
If you use letsencrypt as your reverse proxy you should look at that nginex config not nextvloud. I do not remeber editing any nginx fi;e in nextcloud docker. I've only edited /mnt/user/appdata/nextcloud/www/nextcloud/config/config.php and /mnt/user/appdata/letsencrypt/nginx/site-confs/default If you think you need to have a look at my files I can post them in a few hours.