gacpac

Members
  • Posts

    641
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

3260 profile views

gacpac's Achievements

Enthusiast

Enthusiast (6/14)

36

Reputation

  1. Nice! I'm still for the stable one
  2. Oh wow, Didn't know people were having issues with this. I'm sorry, but in fact if you want to let your dockers access host networks you should go to your dockers settings and check the option "allow access to host networks" Sent from my Pixel 6 Pro using Tapatalk
  3. @snowborder714 @malebron I found it That's I did, and I think it should be added to a F.A.Q somewhere in the top of the forum who knows @linuxserver.io https://github.com/nextcloud/docker/issues/762#issuecomment-504225433
  4. Oh boy, hold in let me look up my history. But long story short it comes down to the swag container, they fixed it in future updates in the container but you have to delete the files in order to pull the new ones with the correct codes.
  5. It's been answered couple times in the forum, you'll probably have to scroll back Sent from my Pixel 6 Pro using Tapatalk
  6. Wow, what can I say. That's unraid being unraid. Sent from my Pixel 6 Pro using Tapatalk
  7. Yup. Same thing that happened to me it drive me crazy for months. Anyhow just curious what is that device you are using nextcloud from? Sent from my Pixel 6 Pro using Tapatalk
  8. I'm curious to know your use case, for using dedicated IP Adresses for both nextcloud and mariadb. I just remember there's a setting that might allow you to access host networks using br0 inside docker settings, but it's not perfect, i still rather have 2 physical nics and go from there.
  9. Hey man i found it This was my problem here, i'm sure you will fix it https://github.com/nextcloud/docker/issues/762#issuecomment-504225433
  10. when you mess with br0 it's part of unraid way of working. the best way to do that is having to nic cards one use it for management and the other one use it for the other networks. Someone can explain better than me, but long story short the docker won't be able to reach that 192.168.2.102. I suggest you look the tutorial from spaceinvaderone in youtube to get a better understanding of why you should use a docker network instead of br0
  11. I really don't have anything else. I do remember, but you probably have to search in the forum because it happened to me that one of the default files from swag had a limitation and after looking over at github the file was updated, so again my solution was to rename the file or move it somewhere else to have a new one downloaded with the error fix.
  12. omg this post is alive. it was a docker issue that i had if i remember correctly. i think i deleted the docker, rebooted the server add it and took it from there
  13. Check your proxy config because by default is more. In my let's encrypt i have this proxy_max_temp_file_size 2048m; client_max_body_size 0; I think 0 means unlimited or not checked. Let me know after that. Also you can modify the nginx.conf inside the nextcloud appdata folder. Additionally, you can safely rename the file, restart the container and let it download updated conf files from github
  14. It's been couple times that nextcloud has crapped out on me. First sign is - 504 gateway time out - console not accesible with error message "OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: process_linux.go:112: executing setns process caused: exit status 1: unknown" I have to reboot my entire unraid to get it working again, but now it's not doing it anymore I really don't know what to do.