skois

Members
  • Posts

    417
  • Joined

  • Last visited

1 Follower

About skois

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

skois's Achievements

Enthusiast

Enthusiast (6/14)

65

Reputation

  1. Tbh I've used mariadb for a while but had some issues. After moving to postgres, never had any problems. Sent from my Mi 10 Pro using Tapatalk
  2. Maybe once a day... Steps to replicate it: 1. I assumed that it was a problem of dockers starting too fast. 2. I tried to have a wait time before they start. But problem appears again. 3. When I **stop** mariaDB2 and and NEXTCLOUD2 and restart it after few seconds, it works again. Could anyone suggest where to look for problems? ---------------- Nextcloud version: `Nextcloud 22.1.1` Operating system and version : `UNRAID Version: 6.9.2 ` Nginx version: `v2.9.9 [emoji2398] 2021` The output of your Nextcloud log in **Admin > Logging**: This is the only error warning I get since it has worked: Sounds like the mariadb is crashing, check the logs for it. In my experience, if it gives 502 without any changes in your Network set-up, it's the DB. Sent from my Mi 10 Pro using Tapatalk
  3. I don't know if there is any tweaks. But there are a lot of layers, so delay will be there.. Sent from my Mi 10 Pro using Tapatalk
  4. You best bet would be mounting the share are external storage (check appstore). * Delete the /data/singleuser/files > /mnt/cloud bind. * Mount the `/mnt/cloud` share as external storage in nextcloud with the external storage app. * Just remember it will show as a folder in your root folder in nextcloud. So you need to add/edit/remove files only inside this folder. All other files in the root dir of nextcloud user profile will be stored in /data > /mnt/cache/appdata/nextcloud/data Also, you might notice some performance loss, and you need a bit of extra config for some apps to not ignore this folder. (e.g. Preview Generator)
  5. Database stores EVERYTHING, except the binaries (files like mp3, jpeg, docx and any other type).
  6. Update instructions is on the 1st post of this thread. And no, updating docker, won't overwrite your updated nextcloud. Nextcloud's server runtime files are stored in the appdata folder Sent from my Mi 10 Pro using Tapatalk
  7. I never figured it out, (not really bothered to).. But it's something with the headers on the reverse proxy, to either trust the cloudflare ip's, or to pass the real client ip to the server. Those should help to start looking around! Btw remember to disable anything like brottli, minify, rocket stuff from cloudflare, or you gonna have ui problems, like missing login form etc Sent from my Mi 10 Pro using Tapatalk
  8. 443 -> unraidip:swaggerport Sent from my Mi 10 Pro using Tapatalk
  9. It's the "correct" way, but should work without also Sent from my Mi 10 Pro using Tapatalk
  10. Ip will be the same, port will be the port of swag, not nextclouds Sent from my Mi 10 Pro using Tapatalk
  11. Check your port forward and make sure that it points to your swag container not to your nextcloud container.
  12. Try adding those in the photo `extra_params` variable have the following `--o:welcome.enable=false --o:user_interface.mode=notebookbar --o:ssl.enable=false --o:ssl.termination=true` I also have a variable `server_name` which have `collabora\.mydomain\.com`
  13. 1. https://www.youtube.com/watch?v=I0lhZc25Sro 2. https://www.youtube.com/watch?v=qnEuHKdf7N0 I'll advice 1st watching both videos and then go apply it. Because there is some changes from lets encrypt to swag. After having reverse proxy on your nextcloud, it should resolve all the warnings you have right now.
  14. First, try 6.4.10.9 (not .3) Second on your collabora docker template, try changing from cloud\\.domain\\.com to cloud\.domain\.com (single backslash), I think this was a change introduced in 6.4.9.* but was still backwards compatible.