TheIstar
Members
-
Joined
-
Last visited
Everything posted by TheIstar
-
He probably means the continue button you see after reviewing the changelog (after pressing update on the update available notification). I just had the same issue. Using the Update OS button on the Tools page however did work for me without issues.
-
Does this plugin force patch your system automatically? I don't see any setting that related to automatic installs or alerting or anything like that. Would be good to have some clarity on that as many people don't like automatic patching, even if they are security patches. Especially if the plugin is going to be included in future releases.
-
In order to improve performance between some of my servers and Unraid I setup the server vlan in unraid and assigned Unraid a static IP on the vlan subnet. While the primary interface is on a different subnet. So now my main ethernet interface is reachable in ip: 10.0.0.20 And I have a vlan setup with ip: 10.10.10.100 as well Mounting a share using 10.0.0.20 goes fine however trying to mount the same share on the same machine using 10.10.10.100 times out. Checking exports I found the shares are exported to both 10.0.0.20 and 10.10.10.100: showmount --exports 10.0.0.20 Export list for 10.0.0.20: /mnt/user/proxmox 10.10.10.9,10.10.10.7,10.10.10.6,10.10.10.5 showmount --exports 10.10.10.100 Export list for 10.10.10.100: /mnt/user/proxmox 10.10.10.9,10.10.10.7,10.10.10.6,10.10.10.5 So it seems NFS is exporting the shares as they should. However, when I do a port scan with netmap it seems the NFS service is either not listening or the port is closed on ip 10.10.10.100 Scan from 10.0.0.20 shows: 139/tcp open netbios-ssn Samba smbd 4.6.2 445/tcp open netbios-ssn Samba smbd 4.6.2 2049/tcp open nfs 3-4 (RPC #100003) 3551/tcp open apcupsd apcupsd 3702/tcp open tcpwrapped 5355/tcp open tcpwrapped Scan from 10.10.10.100 shows: 139/tcp open netbios-ssn Samba smbd 4.6.2 445/tcp open netbios-ssn Samba smbd 4.6.2 3551/tcp open apcupsd apcupsd 3702/tcp open tcpwrapped 5355/tcp open tcpwrapped As can be seen port 2049/tcp is not responding on 10.10.10.100 while it is responding on 10.0.0.20 As the folders are exported in NFS and Samba seems to be working properly on both IP's I can only assume this is not intended behavior. Hence filing a bug report.
-
This is awesome! Thanks for that.
-
Yes, it would be great if it worked like that, but as other people have also already pointed out, the move on a schedule does not seem to move all files anymore unless the cache is filled to the percentage you set. That is why I asked what the use of it is now.
-
Maybe I am not understanding the option right, but what is the added value of the "Force move of files on a schedule" if it does the exact same thing as the mover schedule under the normal mover settings. They way I had this setup before was that the normal mover settings checked every hour if the cache was over a certain threshold and if it was it would move files off. That way the cache never became totally full and this was ideal to prevent issues with vm's, dockers or app data. But it would only do this if it was really needed. And then in the night I had the force move all files running so it moved all files to the array when the server was not in use and was not bothering anyone. They way the plugin is setup now there seems now way for me to keep this functionality? Or am I missing something here or misunderstanding something? Is there a reason this is no longer possible? Would it not be possible to have the force move option invoke the old mover? I am asking to see how to best use this new plugin functionality as currently I might just not understand it.
-
Any change of getting is functionality back? As it is now the force move option does not do much and I really prefer to move the files of my cache in the night instead of during the day when it fills up and the array is in use.
-
Aah yes I found it. So if I would set those myself when first running the container would that overwrite those in the file, or would the file overwrite whatever I set in the run command?
-
Hi Saarg, I never said it was not supported, I only pointed out that the developer warns against using it. I think it is normal then for me to worry that in some months I might have an issue where my data is stuck in a not supported database. It's called planning ahead. And again, I was not criticizing anyone for it I was only asking why this decision was made and if it was deliberate. And if there was a way for me to setup a different DB if I want to. I did see the config file, however I am/was worried it might be problematic to edit this as I can only edit this after first starting the container. Not sure if changing the DB at that point might break something. Do you know what env vars are missing?
-
Question regarding usage of this container. It seems this container comes with a SQlight DB already set up. However the documentation of Wiki.js actually advised not to use SQlight and use PostegrSQL instead. In fact it mentions: So the question is, does this container support the use of other DB back-ends? And if yes, does it use the environment variables mentioned in the official documentation or does it work differently? Another reason to use PostegreSQL would be the search function as the one included with SQlite is much more limited compared to PostegreSQL. As normally @linuxserver.io knows what it is doing I would be curious to know why the choice for SQLight was made and the use of another DB not documented. Was this a deliberate choice or maybe an oversight? Not criticism, just genuine curiosity as I would like to understand the container and it's use case better.
-
I just added the following line to my letsencrypt nginx proxy config: proxy_temp_path /config/proxytemp 1 2 This way it just creates a sub folder called proxytemp in the letsencrypt folder in appdata.
-
Did you change it here? :
-
Since it is only when downloading/uploading it might just be the temp folder. Did you set proxy_temp_path in your nginx config in your reverse proxy? Are you even using a reverse proxy?
-
In the template add a new port 6595. You will also need to change the port for the webui (visible when you enable advanced). If it still does not work try a force update. remember it will take some time to install the software again (you can check to log to see the progress)/.
-
Same for me. Did you get this sorted?
-
Just downloaded and installed the Deemix docker and it looks really cool. Just having 1 issues, when music is downloaded and I want to change something or remove something by accessing the share it seems I do not have the rights to do it. Looks like only the original user (nobody) has the rights to change or delete the files. Would it be possible to change it so all users can modify/delete files?
-
Any news on this?
-
Sure, I can test. What kind of issues where you facing?
-
Any word on this working with quicksync/QSV now it works with nvenc? The template seems to suggest it already does...
-
I found a way to get it running in Unraid !!!! In advanced view under extra parameters put: --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 This makes sure you run the container with the right UID and GID Then under Post Arguments put: && docker exec -u 0 Nextcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars' This adds the right umask to the envvars file. Now new files created have the right access rights for Unraid: Please let me know what you think?
-
Does this mean I have to run this exec manually after each pull myself? Or will you automate this somehow? Not sure I understand correctly.
-
No scripting expert, but I guess something like this would work: grep -q 'umask 000' '/etc/apache2/envvars' || echo "umask 000" >> /etc/apache2/envvars I tested it and it seems to run as expected. Also adding this line gives the required rights to everybody. I could edit and change files created by Nextcloud without issues.
-
I already set the docker user to 99:100. The problem is that the umask of netxcloud user is set to 022. Which means only the user has write permissions and not the group. It should be 000 for Unraid. As I said in my previous post, you can do this by editing a file inside of the docker. But Any update to the docket would overwrite this.
-
Further investigation shows the Linux Server Docker actually has the same behavior if you add the unraid shares as local Storage.. As they respect the UID and GID it seems there is more to it then just adding this to the docker. I think getting SMB to work in the docker would probably be the best/easiest solution. But I have not figured out how to do this yet... So, any help or insight here is appreciate.
-
Thanks for the reply, I did already try to add these to the template. however this did not work. it seems the container is not setup to work with the variables? some googling let me to add this to the extra parameters: --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 However, even though now the correct user is running with the correct group, it looks like it does not have the correct umask set. you can change it by bashing into the container and changing it in /etc/apache2/envvars, however, i am afraid any update to the container would overwrite it again. Also it seems a bit overly complicated.. there must be an easier way to do it. I did also try to install the smb client in the container, as it seems this is not included. Adding the shares as an SMB share does grant the correct rights but of course, also here any update would remove the client again. It seems there is a way to add it (see: https://github.com/nextcloud/docker/tree/master/.examples ). However I have no idea how to get this working in unraid.
