jakami99

Not sure if I still can help you but here is my config. Make sure you have the path for the DB right: If the container crashes over and over again, you should check the logs for the reason. It could also help, to remove the container, remove the "traccar" folder from your "/mnt/user/appdata" and reinstall it while providing the path as mentioned I hope you get or got it running

Ass a path, where the container container path is /opt/traccar/data and the host path is /mnt/user/appdata/traccar/data This way your database won't get deleted after a restart

The traccar Docker container is missing a important path. The /opt/traccar/data folder should be mapped to appdata, since it contains the database. Even tho a dedicated MySQL-DB is recommended, it is not good that the testing/default db gets deleted whenever the container gets updated.

Hi Thanks for this project, awesome work. Oddly, I get no Geolocations on the dashboard, but ip-api is enabled. I get the following error in the logs: (redacted IP) W0117 22:44:56.159426 1 client.go:60] Failed to obatin the geohash of 180.xxx.xxx.xxx: Get "http://ip-api.com/json/180.xxx.xx.xxx": dial tcp 0.0.0.0:80: connect: connection refused. Manually accessing the website works fine tho (same IP)... EDIT: The "0.0.0.0" made me curious, and I checked my pihole. Weirdly, ip-api.com was on a blacklist and my current pc wasn't using pihole. Whitelisted it and now everything is working

Okay, thanks. After I edited the unassigned device to "slave option" I had no "unresponsive dashboard" anymore, funny enough this issue started about the same time I started using an old drive for torrenting since I don't need parity on these files and don't want my good drives to be occupied 24/7. Especially because torrenting leads to bad latency, since it needs lots and lots of small file parts. Thanks so far, even tho there was nothing specifically that helped If this issue occurs again, I will kindly say so. Cheers!

Is this an issue that might be related to my current issue?: Jan 14 23:03:01 UNRAID-1337 root: Fix Common Problems: Warning: Docker application qbittorrent has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option

Thanks, I took a look at the provided links. Sadly, nothing related to my issue. The whole troubleshooting guide had nothing about the webserver in general. And for the second resource: I am directly accessing Unraid via the clear IP without SSL over the internal network and/or over the Nginx Reverse Proxy, which was never an issue before. Will still take a look at it and hope to get more info here. Are there troubleshooting steps for the web server I may ask?

48 hours later and again... Don't get past logging in. I really have no idea how to troubleshot this. Keeping the server in safemode for hours is complicated and if it doesn't happen, there is no way for me how to tell which the cause is. Are there any debug modes for the internal webserver of unraid? Anything I could test with tools like curl? Are there any extended logs for nginx, other then the error.log in /var/logs/nginx? Could a reinstall in the usb help?

Netdata looks pretty okay, the only warnings are the following. I am not sure if this is just a symptom, or the root cause. Either the cause or maybe a symptom of the issue.

Sadly it's happening again, login site perfectly works, but logging in or having a valid cookie leads to infinte loading and no HTTP answer to the GET. In "/var/log/nginx/" is only an "error.log". I hope the diagnostics include the non-error nginx logs. unraid-1337-diagnostics-20240109-2033.zip

I have really no idea what is going on, but I want to disagree. There were no steps that can lead to a conclusion, that this was not the software. I got multibit ECC, which is pretty new. But memtest could be a step for the future, if this issue consists. Will take a look at the nginx logs, when this is happening again. Since the login site was working perfectly, but the /Main dashboard wasn't, it might be a plugin, that tries to load.

I will restart without safe mode now and just hope, it won't stop responding again... Thanks tho

Anything I can do, now that I am in safe mode? Unsurprisingly the dashboard is working, it will take a while, until I know if this error still occurs. As I mentioned it always takes some time for the Dashboard to become unresponsive.

Rebooted into safemode unraid-1337-diagnostics-20240108-0209.zip