NY152

Hello Since yesterday, NPM has been shut down for no reason. When I try to restart it, it stays off WITHOUT ANY message in the unRAID WebUI. The log displays this: Please help me to correct this

J'ai plusieurs fois cette erreur :

Hello, For a few days, without any activity (outside of my dockers) being performed, unRAID has become totally inaccessible. The effects are: - A total shutdown of all hard disk activity (the activity LEDs no longer light up at all, only the power supply ones are on) - Inaccessibility of shares - The server IP no longer responds to the ping and no longer appears online on my box - The server has a screen (which displays the unRAID console by default and is used from time to time for the use of VMs (with passthough)), when the server is inaccessible, no more signal is sent to the screen. I looked in the LOGs but I can't find any malfunction that would cause this blackout! Could someone tell me where to look? Thanks in advance

Absolutely all shares are at 0 (empty fields) The problem therefore does not come from the available space.

My server is temporarily saturated, it's true! It will not last, fortunately! The option you mention is not in the page when creating the share, where can I find it?

Sorry for the wait, work kept me pretty busy! Here is the diagnostic archive Please help me ^^ unraid-diagnostics-20230705-1411.zip

Tank's for information !

I'm writing this post because I don't quite understand unraid's policy regarding root and non-root users Why impose root for the WebUI and for SSH? This is a big flaw in my opinion. For those who do a little research, they already know the user to brute-force! The user could at least have the choice to disable root and choose a user instead, at least for SSH, must be able to have a choice right? Not to mention that unraid does not even allow you to configure a fail2ban by default. There is a plugin, but I highly doubt its effectiveness. What do you think ? ____________________________________________________________________________________________________________________ J'écris ce post car je ne comprends pas trop la politique d'unraid concernant root et les utilisateurs non-root Pourquoi imposer root pour la WebUI et pour le SSH ? C'est une grosse faille selon moi. Pour celui qui se renseigne un peu, il connait déjà l'utilisateur à brute-forcer ! L'utilisateur pourrait au moins avoir le choix de désactiver root et choisir un utilisateur à sa place, au moins pour SSH, doit pouvoir avoir le choix non ? Sans compter qu'unraid ne permet même pas de configurer un fail2ban par dafaut. Il existe un plugin, mais je doute grandement de son efficaicté. Qu'en pensez-vous ?

I would very much like to test the tool but when I create my instance, whether I put 'host', 'bridge' or any other 'custom' network, Youtrack starts on the NAS IP and the web interface does not work. If I try to fix the ip, Youtrack simply does not launch with the following error: Server Error Please help me, tank's

I deleted the network.cfg file and that solved the problem, thanks.

It changes absolutely nothing...

Hello, I have a bug since this morning, for plugins, dockers, updates are marked "unavailable". Even the connection with My server has a attention panel. I tried some tests. All sites respond to ping in unRAID except unraid.net and github.com I specify that my DNS are fixed on 1.1.1.1 and 9.9.9.9 (even on my internet box) I tried to deactivate the ipv6, same worries. Do you have an idea to correct the concerns ? Thanks in advance

Hello, For the past 2 days, the password I set for the GUI months and months ago is no longer recognized. How to reset it because I no longer have access to my transfers Thanks to those who will help me.

Hello, I am a user of the Apache-PHP container but I would like to be able to change some PHP values in its INI file but I don't have access to it. Changing the values in the PHP code does not work (tested with upload_max_filesize without success). Changing values in an .htaccess file doesn't work any better, worse, you get a 500 error. Accessing the container via the console does not work for me on my unRAID server. Thanks for helping me with how to fix my problem.

Personally, sometimes the redirections don't work. A reboot fixes the problem but I would like to understand why it doesn't work after a while. In the logs, I have an error concerning certbot : 2021-05-12 12:05:01,023:DEBUG:certbot._internal.log:Exiting abnormally: Traceback (most recent call last): File "/opt/certbot/bin/certbot", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.8/site-packages/certbot/main.py", line 15, in main return internal_main.main(cli_args) File "/usr/lib/python3.8/site-packages/certbot/_internal/main.py", line 1403, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/lib/python3.8/site-packages/certbot/_internal/plugins/disco.py", line 237, in find_all plugin_ep = cls._load_entry_point(entry_point, plugins, with_prefix=False) File "/usr/lib/python3.8/site-packages/certbot/_internal/plugins/disco.py", line 255, in _load_entry_point plugin_ep = PluginEntryPoint(entry_point, with_prefix) File "/usr/lib/python3.8/site-packages/certbot/_internal/plugins/disco.py", line 51, in __init__ self.plugin_cls: interfaces.IPluginFactory = entry_point.load() File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2461, in load self.require(*args, **kwargs) File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2484, in require items = working_set.resolve(reqs, env, installer, extras=self.extras) File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 787, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'future<1,>=0' distribution was not found and is required by dns-lexicon 2021-05-12 12:05:01,023:ERROR:certbot._internal.log:An unexpected error occurred: 2021-05-12 12:05:01,023:ERROR:certbot._internal.log:pkg_resources.DistributionNotFound: The 'future<1,>=0' distribution was If anyone has a solution, I'm interested Thanks

The argument regarding ransomware (this was still an example) is that if a ransonware attacks file encryption, the source of its files (the original therefore) is deleted in favor of the encrypted version, the recycle bin could be a rampart in the sense that we would recover the original! So limiting access to a defined user would make sense. Placing them elsewhere would perhaps be more logical if we listen to you (Samba rights) although I doubt it because, for example, on a Synology NAS, the recycle bin can be limited to only the administrators of the machine so the thing is quite possible no ?

For security reasons, it might be good to have the possibility to set the access authorization to the recycle bin to a single user (who will be considered as administrator (root for example) of the recycle bin) with which we will not connect by sharing. This would act as a safeguard in the event of compromised security (ransonware for example) You can also think about not storing the recycle bin in the share but in a place not accessible to the share !

Hello, would it be possible to have an option to restrict access to the recycle bin to administrators only (or to selected users)?

Hello, Almost 1 year since the release of the last stable version, it's been a long time. When will we have the privilege of seeing the arrival of v6.9 in stable version?

Hello, I have walked through a little thread regarding accessing the recycle bin! It would be good to offer an option that automatically makes the trash folder and its contents completely inaccessible to the logged in user. Why ? For security purposes ! Imagine that the user is the victim of a virus or ransonware, the files in the recycle bin could save hours of work ^^ This is why the configuration of the recycle bin must be able to be configured (a bit like on Synology's DSM in short)

Afin de fixer certains problèmes de droits dans mon serveur, j'ai tenté d'aller dans Tools > New Permissions Que je ne choisisse qu'un seul disque et / ou partage, j'ai ceci : Rien ne s'affiche, j'aimerai comprendre. J'ai beau laisser ce popup une éternité, rien ne s'y affiche et mes droits sont toujours aux fraises ... J'aimerai ne pas casser les droits de mes partages aussi si quelqu'un aurait la commande permettant de fixer tous les disques et tous les partages en SSH, je prends ^^ D'avancer, merci

Hello, I am using ubooquity docker on my unRAID server and would like to add more directories. Only I don't know how to add more from the docker management interface. Could someone enlighten me? Thank you EDIT : Rights problem, resolved

nginx crashes randomly. This can be found in /var/log/nginx/error.log # cat /var/log/nginx/error.log 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to 192.168.0.100:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to [2a01:e0a:2f6:9220::188b:5653]:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to 192.168.0.100:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to [2a01:e0a:2f6:9220::188b:5653]:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to 192.168.0.100:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to [2a01:e0a:2f6:9220::188b:5653]:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to 192.168.0.100:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to [2a01:e0a:2f6:9220::188b:5653]:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to 192.168.0.100:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: bind() to [2a01:e0a:2f6:9220::188b:5653]:8081 failed (98: Address already in use) 2020/07/07 18:33:38 [emerg] 8029#8029: still could not bind() 2020/07/07 21:14:42 [info] 24358#24358: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:143 2020/07/07 21:14:45 [alert] 8297#8297: *15136 open socket #17 left in connection 9 2020/07/07 21:14:45 [alert] 8297#8297: aborting A little help would be appreciated