lsaranto

Got this error when installing: docker run -d --name='NetAlertX' --net='host' --pids-limit 2048 -e TZ="Europe/Helsinki" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ugreen" -e HOST_CONTAINERNAME="NetAlertX" -e 'TCP_PORT_20211'='20211' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:20211]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/jokob-sk/NetAlertX/main/front/img/NetAlertX_logo_notification.png' -v '/mnt/user/containers/netalertx':'/data':'rw' -v '/etc/localtime':'/etc/localtime':'ro' --read-only --cap-drop="ALL" --cap-add="NET_ADMIN" --cap-add="NET_RAW" --cap-add="NET_BIND_SERVICE" --cap-add="CHOWN" --cap-add="SETUID" --cap-add="SETGID" --tmpfs "/tmp:uid=20211,gid=20211,mode=1700,rw,noexec,nosuid,nodev,async,noatime,nodiratime" 'jokobsk/netalertx' 5a8084da852ac695cf0b4c308b69544dcccf9e78adf1c261e8698895c0457db2 docker: Error response from daemon: error while creating mount source path '/etc/localtime': mkdir /etc/localtime: file exists. The command failed.

For a brief moment I thought that this fixed my non-booting Windows 10 VM. It stopped working after I migrated my Unraid server to Ugreen DXP8800 Plus. But the reason why it finally booted, was that I dropped allocated cores to just one. So if anyone knows how I can allocate more, please tell. Also, if I add the extra qemu:commandline tags, it complains about hyperv vpindex support.

Anyone here know what the 'Create symbolically linked views for each user on the clients after file backups' setting does? There are several questions about it in the Urbackup forum, but no answers. I can see "Creating user views..." in the log after a backup, but how can I access it?

Just to check, you do know the path is /gallery/galleries/<your-photos>? Also, you don't need symlinks. You can just create another mount for the photos in the Piwigo container template. So /mnt/user/filerun/user-files/sach points to /gallery/galleries.

I haven't updated Piwigo in a while and I hadn't seen that announcement. I used to be the guy who always ran the latest versions, preferably even beta. Not anymore. I haven't touched those configs so one would expect those configs that are in the container to work. Or there should be an instructions how to migrate.

Maybe you just made a typo in the post, but mine is just named 'default' (no .conf extension). Here's its content: server { listen 80 default_server; listen 443 ssl; root /config/www/gallery; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/cert.crt; ssl_certificate_key /config/keys/cert.key; client_max_body_size 0; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php5-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php5-fpm: #fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } }

I post this update here. Maybe it will help someone someday. So it seems my issue was caused by some plugin. I began to suspect it after I realized Unraid was showing me the same notification about plugins having an update available, even though I had already done the update (several times) successfully. Every time after doing the updates the flash drive lost it's GUID until I rebooted the server. There were 3 plugins in the notification: Community applications, Unassigned drives and OpenVPN Server TAP. I'm pretty sure we can ignore the first two. I also may have had both old and new versions of USB Manager installed (which I know I should not have had). I also tried booting into Safe mode and the system ran fine. So my solution was to rename /config/plugins directory on the flash drive and create a new one. I then copied back just the user scripts and dockerman directories. All other important plugins I reinstalled via GUI.

I just now tested reading and writing to the flash and it was fine at least at this moment. Of course I'm not going to do any changes to the system in its current state., but it's good to have a running system as my smart home runs on it. I think this behaviour is better than what I had before, when my previous flash failed. It just crashed the whole system. I couldn't find anything about the cause in the logs. The only way I knew it was the flash drive was because it wouldn't boot with just a reset. A full power off was needed. Then it booted fine again and the system ran for about a week or so until it crashed the same way again.

I'm having repeating troubles with my USB flash drives. I've already switched drives twice, but the troubles won't go away. With the current drive, after a boot, it shows the flash GUID ok and the license is validated, but after a while the GUID changes to all zeros and Unraid shows BLACKLISTED in the top right corner of the GUI. However Unraid and the array seem to continue to operate normally. I don't have any reliable spare (new) USB drives and it's gonna take a few days to get one. What are the consequences if I just keep running Unraid like this? I believe the array wouldn't start if the license doesn't match the drive GUID, but like I said the GUID is fine after every boot (so far) and the array starts along with everything else. So far I've noticed that I can't remote login with SSH and VMs won't start after it fails the GUID. Are there other disabled features? Or is there something more serious that can happen?

I have to disagree with this. I have a Sandisk Blade drive that worked fine for 5-6 weeks. Then it became blacklisted showing all zeros in the GUID. If I reboot, it works fine and shows a valid GUID and the license is ok. It seems to lose the GUID again in 12-24 hours. I'm now flashing a second Blade. We'll see how long this one lasts. I originally had one of those Sandisk Fit drives. It started to act up in march after about two years. First the whole system would appear to be crashed. It's a headless system so I don't know if it would have been possible to access it locally, but I was not able to access it remotely (SSH, webUI, dockers, VMs). Sometimes it appeared that some network services kept working. My guess is, if there was an open network connection, it might stay running, but it was not possible to make new connections. After a reboot, the boot process would hang when it tried to read the root image from the flash drive. Full shutdown would result to a successful boot and perfectly running system for a few days or even weeks. Then another crash. As these Sandisk Blade drives (16 GB) did ok in the SpaceInvaderOne's video I bought a few of them from Amazon.de. IIRC, there was also some availability issues with the drives that did better in the test. Sadly I missed this post.

No, I'm running 6.9.2.

I had to change my Unraid USB drive and I lost my OpenVPN setup. I managed to grab and install the forked (TAP) server plugin linked a few post above. It's been running fine for a month or so. Yesterday I rebooted the Unraid server and now OpenVPN won't start. The logs showed no error, but I copied the startup command shown in the log /usr/sbin/openvpn --writepid /var/run/openvpnserver/openvpnserver.pid --config /mnt/user/appdata/openVPNserver/openvpnserver.ovpn --script-security 2 --daemon and ran it in shell. It gave an error: /usr/sbin/openvpn: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory I created a symbolic link for the file in '/usr/lib64'. It then complained about another file: /usr/sbin/openvpn: error while loading shared libraries: libssl.so.1: cannot open shared object file: No such file or directory Again I created a symbolic link for it. Then it gave an error: /usr/sbin/openvpn: symbol lookup error: /usr/sbin/openvpn: undefined symbol: SSL_library_init This I don't know how to fix. I'm guessing it's some kind of library mismatch. I don't remember updating anything related to either Unraid or OpenVPN. So I don't understand what broke or why.

On my WG settings page I have this note when I select tunneled access: "this must be the only peer in the tunnel and sole active tunnel when in use". So according to this, you can't use both at the same time. To me this sounds like a major restriction. For some reason in my gui most of the settings for tunneled access are different then what is shown in the guide(s). And the eye icon to show and download the peer setting is disabled.

I think you have the same issue as me. You need to add another path mapping in the container's configuration. See my post above.

I've had OpenVPN installed and running for a couple of years. Somehow I had lost the x attribute and wasn't able to add new clients. Your post hinted me to check it and it fixed my issue.