Rich Drinan

I was running 7.2 RC1 and then upgraded to RC2 with no issues. I just upgraded to stable 7.2 and it boots but the web service isn't working. I can ping fine from the console and can ssh in. Google helped me to get a login screen via the following but as soon as I login and it tries to load /main, I get a 500 error. > /etc/rc.d/rc.docker stop /etc/rc.d/rc.php-fpm start /etc/rc.d/rc.nginx start I have removed the .cfg files in /boot/config/ for docker, domain, disk, and share but nothing seems to be working. /usr/local/sbin/emhttpd does not exist - should it and it just was a failed upgrade?

Thanks - I did install user scripts and created the script as instructed. I actually got the container to run but by changing the container path as I listed above - which was to get around a permissions issue similar to the other two people that had permission errors. I don't know what the ramifications are of my changing to /var/usr/~. Since at least the last 3 people {starting with @pinion in March) had the same issue with no commentary on the "right" way to fix it, I was wondering if this thread wasn't monitored - no offense intended though.

Is this app/thread abandoned? It looks like my issue was exactly the same as @pinion and likely @wolfnz although the template version is different - same basic issue. I haven't seen any responses to suggest it is being investigated - just wondering.

I was just trying to get this to work on UnRaid 6.10.3 - new config. I got the access denied error trying create the node environment. After searching the web I saw someone change the path to /var/lib/elasticsearch/data and it worked so I edited the docker image and changed that path for only the container path but left /mnt/user/appdata for host path and default value. It seems to be working now but I confess I don't know if this is a viable (supportable) config. Can anyone validate if it makes sense that I should have to do this - possibly due to new defaults or something in 6.10.3?