aptalca

You're right. I'm assuming you guys are on the new beta and it doesn't fill in that field with the default tcp. The stable version does. Also posted here: http://lime-technology.com/forum/index.php?topic=39413.msg455745.msg#455745

Hmm. That's strange because someone else is having the same exact issue with the letsencrypt container. It seems like an unraid issue. Which unraid version are you on? Not at my server to check, but I don't think that the trailing / after the port should be there. Good eye, that's the problem. My xmls leave the protocol field blank and the dockerman fills it with tcp. It seems that the new unraid (I'm assuming folks updated to the latest beta) leaves it blank and it causes the issue

Someone is having the same error message with a different container: http://lime-technology.com/forum/index.php?topic=39413.msg455664.msg#455664 It might suggest an unraid problem

Hmm. That's strange because someone else is having the same exact issue with the letsencrypt container. It seems like an unraid issue. Which unraid version are you on?

Something is wrong. Did you try rebooting unraid after deleting the container? If that doesn't work, I'd suggest asking jonp in the unraid bugs sub forum

Ok, i tried to install it on cache and on one of my disks directly. I get the same error. I'm confused about your logs. The first one you posted showed a fail2ban error which I fixed in the latest update, but apart from that it seems to have installed the container. But the second log shows a failed container creation?? Is that snippet taken from the unraid's container install screen? If so, then unraid seems to have had an issue correctly downloading the image and creating the container from it. Can you describe what happens? Thanks When i try to install the docker now, i get the error message. I see nothing in the unraid log.. But i see, that there is some data left in the system, see the picture. I deleted the folder (/appdata/nginx) on the system via ssh. But there must be some data somewhere else. Maybe if i can delete this data, i can try a new fresh install. If i try to install other dockers, i have no problem. If you left click on the orphan image's pic and select remove, they should be deleted. Then you should be able to install from scratch

Ok, i tried to install it on cache and on one of my disks directly. I get the same error. I'm confused about your logs. The first one you posted showed a fail2ban error which I fixed in the latest update, but apart from that it seems to have installed the container. But the second log shows a failed container creation?? Is that snippet taken from the unraid's container install screen? If so, then unraid seems to have had an issue correctly downloading the image and creating the container from it. Can you describe what happens? Thanks

The script is used to externally trigger an event on zoneminder (e.g. security alarm going off). The script needs to be always running for this to occur. The default behaviour is that it's not running. As a temporary fix I've just added it to the zoneminder init.d script which seems to do the job. Cheers. Zoneminder wiki says that the script is called when you turn on opt_triggers in the settings. Does that not work for you? https://wiki.zoneminder.com/How_to_use_your_external_camera's_motion_detection_with_ZM Thanks

Can you post the log from the terminal? That log doesn't show any errors with letsencrypt or nginx, only fail2ban, which wouldn't explain why the webpage isn't coming up Hello Again, i tried downloading the docker again and now i have the following error: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Nginx-letsencrypt" --net="bridge" --privileged="true" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e EMAIL="[email protected]" -e URL="xxxxx.xx" -e SUBDOMAINS="www" -p 80:80/ -p 443:443/ -v "/mnt/user/appdata/Nginx-letsencrypt":"/config":rw aptalca/nginx-letsencrypt docker: Invalid proto: . See '/usr/bin/docker run --help'. The command failed. Try changing the config path to /mnt/cache/appdata/nginx if your appdata share is a cache only share. If not, put it on a single disk and try /mnt/diskX/appdata/nginx Many dockers have issues when the config folder is on a user share. It's an unraid issue

Awesome thanks! Would it be possible to have the option of zmtrigger.pl (/usr/bin/zmtrigger.pl) always running? Could you elaborate on this? What's the current behavior and what is the desired? Thanks

Thanks for the heads up. Fixed in the new update.

Well, many containers don't work if the path is a user share. Read the last few posts in this thread, most are about the same issue, which is a bug in unraid If that share you're using is a cache only share, you just have to change the name in the container settings, not the location

For all zoneminder fans, version 1.29 is out. But it's a separate container. Due to the extensive changes in the new version, it was near impossible to update a 1.28 version in place. So you'll have to install this separate container and set it up from scratch. Don't try to install it using the same config folder with existing data, it won't work. To be honest, I wasn't even able to update my existing install to 1.29 no matter how hard I tried (without deleting the existing data), so there was no way I could do it for all the existing users with different configs. Let me know if the new one has any issues

What path did you use for the config folder?

Did you wait long enough? It updates meteor on start and depending on how slow meteor's servers are that day, it can take up to an hour for that first update (usually a couple of minutes) The log suggests it has not done updating yet

Probably a permissions issue with smb I actually mount the whole unraid drive in dolphin as /mnt:/mnt so I can move things natively and not through smb open the advanced view in container settings and you'll see the resolution variables as well as the uid and guid if you want to run it with root permissions

I just tested it again and it lets me cut and paste as well as move by dragging in split screen. Are you getting an error? Do you have write permission in the folders or on the file? Are you running it as nobody or root?

Still working on it

johnodon, I wish you didn't delete the github repo for this. I was gonna send a patch to externalize the zap2xml perl script as unevent suggested: have the user download it and place into the the config folder. Then there would be no issue with the author and the docker would simply be a distinct wrapper. Anyway to undelete?

I always check the PSU first. I have a small Dell power supply tester, which tests the connections but doesn't put a load test on it. I re-seat the controller cards and memory if I have to and while I'm in the case do check all the cables. Any luck? I'll do that when I get home. Thanks for the suggestions

That's a great idea. I'll direct that to a file on the cache drive, which is always spinning anyway. Thanks

Not home right now, but unlikely. The router gui shows that it's been up for 25 days. And the server is connected to a ups which is pretty reliable. How are you connecting to your phone from the your server at home? EDIT: If you are allowing direct access to your server, you could be the victim of a practical joker who just restarted your server rather then doing something far more malicious. Haha that would be cruel, but no I'm using openvpn (docker on unraid) and I also have a pptp server on an old router. The server is not directly accesible from the internet

Not home right now, but unlikely. The router gui shows that it's been up for 25 days. And the server is connected to a ups which is pretty reliable.

Uh oh!!! I just had a crash and a server restart. No idea why. I was streaming plex on my phone during my lunch break. All of a sudden, I lost connection. Thinking it was my phone, I was trying to reconnect to the plex server, etc. And a couple of minutes later, I got an e-mail saying a parity check was started. It turns out, my server restarted itself, possibly due to a crash. I have no log entries (wiped with the memory I guess). It is concerning because I just updated to 6.1.9 the night before and now this happens. The last entry in the log was the shutdown during the update to 6.1.9 the night before. And it picks up after the restart today. In between is lost. Unraid terminal shows uptime of 20 minutes, so I'm assuming it was a restart of the server as opposed to the array restarting. Any ideas for further troubleshooting? I am currently running a parity check. My server hadn't had any issues in a really long time. I'm not happy, I wish the logs were saved on a disk so I could see what went wrong. Thanks

Can you post the log from the terminal? That log doesn't show any errors with letsencrypt or nginx, only fail2ban, which wouldn't explain why the webpage isn't coming up