spiderben25

Hi, Since updating to Unraid 6.12.2 and switching to this Appdata app, I have a problem creating a backup. It seems like the "Save external volume" feature is not working. When the app tries to backup for example Binhex Krusader docker, which contain a large /mnt mount, it sees it as an external volume, the option to save it is toggled to No as default, but the backup process takes forever and it seems like it's creating a very large tar files despite the actual /mnt/appdata/binhex-krusader folder is only a few kb. Can you help me with this one? Thanks.

Thanks, will try it, it's a lot different from the sample one.

Hi, Since updating my swag setup (updating the docker container and regenerating config file from samples) I can't use Onlyoffice in Nextcloud. Documentserver.mydomain.net works, I get the welcome page. On Nextcloud Onlyoffice administration page, everything works too. But when I open a file I get this error : https://rehost.diberie.com/Picture/Get/f/97332 When investing using Chrome F12 function, here is what I get: https://rehost.diberie.com/Picture/Get/f/97331 First I thought it was an X Frame option that was causing the problem but removing the header from my nginx conf file didn't solve it. When I inspect the blocked content it doesn't show any "same origin" header so I don't think the problem is from that setting. https://rehost.diberie.com/Picture/Get/f/97330 Here is my documentserver.subdomain.conf file: ## Version 2022/09/08 # Make sure that your dns has a cname set for onlyoffice named "documentserver" # Make sure that the onlyoffice documentserver container is named "documentserver" server { listen 443 ssl; listen [::]:443 ssl; server_name documentserver.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth (requires ldap-location.conf in the location block) #include /config/nginx/ldap-server.conf; # enable for Authelia (requires authelia-location.conf in the location block) #include /config/nginx/authelia-server.conf; location / { #enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable for ldap auth (requires ldap-server.conf in the server block) #include /config/nginx/ldap-location.conf; # enable for Authelia (requires authelia-server.conf in the server block) #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app documentserver; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Can anyone help me? I can provide extra info if needed. Thanks.

Hi, Could you share your documentserver.subdomain.conf file? I can't get it to work since last update.

Tried some more things today. First of all, connection between Nextcloud and OnlyOffice was ok (you can check this by using "occ onlyoffice:documentserver --check" command in Nextcloud docker command prompt). When I tried to open a file, I got a "Onlyoffice cannot be reached" error. I got more explanation on this error by pressing F12 in Chrome. The source of the error was "too many redirects". Than I edited my swag/nginx/proxy.conf swag file like this: proxy_redirect off; #proxy_redirect http:// $scheme://; to turn off the redirecting system. Tried again, this time it doesn't work and the error Chrome shows is "Refused to display 'https://documentserver.mydomain.net/' in a frame because it set 'X-Frame-Options' to 'sameorigin'. I tried to comment out "add_header X-Frame-Options "SAMEORIGIN" always;" line in /swag/nginx/ssl.conf but it didn't do anything. Can anyone help me with this? I will roll back to Collabora in the mean time.

You can check which files are deprecated by looking at swag log on the Docker tab of your unraid webui. Then you can delete (I strongly recommend you make a backup first) them, they are located in /mnt/user/appdata/swag/nginx. The next time you will restart the swag container it will create up to date config files. You can also do this to the nginx config files in /mnt/user/appdata/nextcloud/nginx. Same warnings here. Of course if you made custom changes in said files you will have to make them again. An easy way to check that is to compare side by side the old and new config file, with notepad++ for instance.

Hi, My issues were resolved by updating all of the conf file in my swag nginx folder. Some were really old (2020) and I think updating to Nextcloud 25 might have cause incompatibilities. Now Nextcloud is working fine using the latest Linuxserver docker image. New problem: I can't access Onlyoffice in Nextcloud. When I open a docx file I get a blank error screen saying "documentserver.myserver" doesn't allow connection. I didn't change anything in the Onlyoffice settings panel and I can access the welcome page. I think something is messed up in my swag config files but can't figure it out.

Same problem here, since updating Docker container and upgrading Nextcloud to 25.0.0, getting 504 error whenever I want to access a file... Tried to rolled back to the older repo version but that doesn't work. What would be the best thing to do? Migrate both mariadb and Nextcloud to the official Docker repos instead of Linuxserver? Is there an easy way to do this?

I think local subnet detection is faulty since last Emby update. I had to enable remote access to get access back, then in the network settings I manually added my local network subnet and only then I could disable remote access. Before doing that last bit, the server info page showed the internal network Docker address (176.something) instead of the usual 192.168.0.xxx.

Hello, Same problem here since an update a few days ago. Last update didn’t fix it. Did you find a solution? Emby has been working fine for months and now all I’m getting is a Forbidden message when trying to access the web ui. EDIT : this did the trick https://emby.media/community/index.php?/topic/103521-docker/ I guess since Emby is running in Docker it does not recognize properly the local subnet as local.

Hi, I'm having the exact same problem. Did you find a solution? Thanks! EDIT : seems like it's a permission issue. When I SSH as root I can see all the files mounted but they are owned by root:root. I'll try to edit the mount script accordingly.

Thanks. Seems like it's not exactly what I have been looking for indeed.

Hi, would love to see an update for this too

Thanks for this quick tutorial, very useful!

I tried a few times. It seems like when the nextcloud share is set as a public share, I have read/write permissions on my nextcloud folder when I access it through SMB and put a dummy user/password combination. When it is set a a private share, I connect to it using my unraid user (which has R/W access) and can access only the parent files. The files under nextcloud/user/files are read only from my unraid user and r/w with the unraid/nobody user. Is there a solution beside setting the share to public?

+1, would love some answer on this. I'm running into another problem. When I tried to access my nextcloud user files using Windows Explorer via SMB (\\ipofmyunraidserver\nextcloud\user), everything is read-only. When I'm in the parent folder (\\ipofmyunraidserver\nextcloud) I have no problem to write files. The nextcloud share is set up as a private share on Unraid and of course I'm using the right user/password combination. So I guess nextcloud is not using Unraid permission structure. Is there a solution to this? Basically, when I'm at home I want to access the files on my Nextcloud file structure like I would do with any unraid smb share, via Windows explorer. And when I'm away or on a mobile device using Nextcloud app, access them through Nextcloud.

Thanks for your feedback. I'm considering buying this motherboard for a new build. I heard on some forum posts that there might be trouble installing CPU heatsink when all RAM slots are populated. Did you experience this issue? And do all aftermarket CPU heatsinks require a custom back-plate?