Bait Fish

For mine, those three changes almost got me there. For targetHostname: host.docker.internal I had to change host.docker.internal to my server's actual LAN IP (like 192.168.x.x). That's when mine worked. Note I am on :latest

I gave it a very large parent folder and it took a very long time to scan. I came back to the webui once in a while then forgot about it. Much later now, I see that it worked. Pretty neat display. Regarding file path, I did not get the error your log shows. I left SCAN_DIRECTORIES set to /media-server as the template defaulted. File Path container path is still /media-server and I pointed that to /mnt/user/data/media/ Here's my run command for comparison docker run -d --name='StoryScan' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Homer" -e HOST_CONTAINERNAME="StoryScan" -e 'SCAN_DIRECTORIES'='/media-server' -e 'TREEMAP_MAX_NODES'='20000' -e 'TREEMAP_MAX_DEPTH'='5' -e 'TREEMAP_LIGHT_THRESHOLD'='5000' -e 'TREEMAP_MODERATE_THRESHOLD'='15000' -e 'TREEMAP_AGGRESSIVE_THRESHOLD'='50000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3000]/' -p '3455:3000/tcp' -v '/mnt/user/data/media/':'/media-server':'ro' 'ghcr.io/unknowncall/storyscan:latest'

For the StoryScan template, WebUI is empty and Unraid does not appear for the container. After ticking ONthe Advanced switch, I added http://[IP]:[PORT:3000]/ and made it work. [LOL, just noticed luzankia post similar]

JorgeB, thanks for leading me to a solution. It seems so far not to have been the plugin. I rebooted and removed the plugin as advised. The system ran fine until I again ran the (new, untested) user script I mentioned earlier. I was able to cause the 500 error immediately each time the script was run subsequently. And it caused the 500 error immediately each time. It seems it was causing i/o overload too quickly. Got rid of the offending operation and the script is again running and Unraid remains accessible.

Hi all. Looking for guidance for my Unraid GUI error. Running 7.0.1 and ran into this problem last night. No dashboard web access, no login prompt. It just displays a white error page, "500 Internal Server Error" and "nginx" below that. I usually access my Unraid via this link, http://homer/Dashboard Using the IP instead of homer results in same. Docker containers are still functioning and accessible. VM service disabled. I do have SSH access via PuTTY. I have not yetrebooted, and copied the syslog (attached). Also attached is the nginx error log from /var/log/nginx I reviewed https://docs.unraid.net/unraid-os/troubleshooting/diagnostics-information/ . But running "diagnostics" errors for me like this, "-bash: diagnostics: command not found". And which does not find diagnostics for me showing this, "which: no diagnostics in (/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin)". I first found the condition last night before bed, in the 2200 hour. There was a User Script that was set to run at 22:03 that I wanted to check on. That script moves files between drives. Coincidence likely, but that's when I first saw the 500 error. This morning I attempted "/etc/rc.d/rc.php-fpm restart" and "/etc/rc.d/rc.nginx restart". Those appeared to run successfully, and the 500 error persists. syslog.log nginx_error.log

Having used screen, I was looking to use it or similar again. Search found your TTM. This is awesome, thanks! I love the integration with Unraid. It has been working great and is very easy use.

radarbox did not show on CA as far as I can find. I tried manually making a container for it but failed. Could you look into your template's CA status? main, fr24, & FA have been working great! Edit months later: adsb-radarbox showed on the CA, installed, and working. I had to do the fake RPi serial number workaround per the log's direction. And, the other containers continue to work great. Thanks, Unknowncall!

Thanks for putting these up. I assume all of the blacklisting is either not needed or already done. My RPi install broke early this year and I never got back to it. Worked like a charm! [no, see update below] Using adsb-main of course, and adsb-fr24feed & adsb-flightaware. Can you put up a container for RadarBox too, please? Those are the three I was contributing to last. I'm still not sure about ads-b exchange after they got sold last year. Update: Actually, I failed to spot that adsb-flightaware is not happy actually. Trying to figure it out. The below keeps repeating (after my last try). I have to step away for other commitments now. Will continue later. Seems odd given fr24feed shows aircraft data sent, but not flightwaware. UPDATE 2, solved I think: Looks like I misinterpreted the "BEASTHOST" container setting. It needed an IP (192.168.x.x), not "Specify an external BEAST protocol provider (dump1090/readsb/etc)." I had readsb input there. Then it would not resolve the host. Rookie mistake. I now see data on flightware

This is probably a no brainer for some, maybe not others. This app has been blacklisted in CA with no apparent updates, while the project page shows continuing update progress. I changed the container settings below and appear to have the latest version now. Repository: ghcr.io/swing-opensource/swingmusic:latest Registry URL: https://ghcr.io/swing-opensource/swingmusic:latest

I had trouble viewing the GUI for the vnStat container. Defaults were left in the template during install except Network Type. I had set that to my custom network. The problem after first install was that clicking the WebUI link in Unraid would bring up a blank page using Chrome on my PC. This was the only machine/browser I tried. The URL listed was something link blocked/blank. Sorry. I did not capture the exact detail. This behaved differently from other containers. I tested using my machine's local IP and the container port. That too was not successful. I added this to the container and was able to reach the GUI. Click Add another Path, Port, Variable, Label or Device and set the port details. Config Type: Port Name: Host Port for 8685 Container Port: 8685 Host Port: 8685 Default Value: 8685 Connection Type: TCP Once that was done it worked for me. Note that I had changed one other container before this success. I adjusted the WebUI setting (under advanced view). The default was "http://[IP]:8685/". I changed it to "http://[IP]:[PORT:8685]" to match other functioning containers on my system. I'm not sure if that had any bearing on getting the GUI to show. One last change was it had an inactive interface as far as I can tell. So after issuing these commands, my only active interface, eth0, was left. The two command issued start with vnstat. / # vnstat --iflist Available interfaces: tunl0 eth0 (10000 Mbit) / # vnstat -i tunl0 --remove --force Interface "tunl0" removed from database. The interface will no longer be monitored. Use --add if monitoring the interface is again needed. / # Hope this helps others.

I issued the commands in an unraid command terminal first. Then install the container.

Worked for me like B4rny metioned. The 'Before you install' instructions listed in overview section of the container settings. One possible issue. The container defaults to appdata to /mnt/user/appdata/swing-music/ (hyphenated) which is different from the instructions ("cd swingmusic"). So, changed appdata to match where it built to.

I am so grateful. Thanks, many times over, trurl.

The latest diags. homer-diagnostics-20230103-1905.zip

I ran manually mover probably 10 pm, just hours before the troubles seemed to start. I'm thinking that's not a bad number.