Seige

I do see those lines in the log as well. Not sure if it has anything to do with geoip2 or not

The LuaJIT error seems to be gone since the last push?! Thanks for taking care of that, if it is not just on my end 👍

Would it be possible to run multiple instances of the letsencrypt container? All instances would have to have the same port mapping (i presume). Would this be possible by defining custom docker networks for each instance of letsencrypt and would http validation still work? Thank you for the help!

I have the same issue, always comes back with "0 B pulled" on all of my containers. I think amazonaws have some issues, tracert does time out in my case, also.

These ports are required for running TS: 9987 (UDP) 10011 (TCP) 30033 (TCP) (for file transfers) Did you specify the internal ports and protocols correctly? In what network type mode are you running the container? You might want to try it in "host". The error message "Unable to open /config/licensekey.dat, falling back to limited functionality" is shown, because you have not purchased a full server licese and are operating a server which can only host up to 32 clients (i.e. limited functionality). Also you might want to consider removing the "enable reporting to server list" option in the server settings, or you server will be listed in their public server list. If you are still having issues you can also test the official TS docker. There is a short guide I wrote, just in case.

This is a very brief description of your problem. What is the exact error in the log? If it used to work and now is suddenly broken, it might be because of an issue of your port 80 routing (at least in my experience this is very often the culprit). Do you know how to access the docker command line and run a cert renewal test? This usually gives you a more detailed error message.

It is working again, thank you!

For a while now, I also get the array index out of range error, when trying to run a benchmark. It does not spin up any drives. Scanning works fine. Here is a screenshor of the error: I tried to reboot the server and pulled a fresh image with a new appdata folder. No changes. Do you have any idea what might cause this? Thank you!

How is you M1015 installed? These controller gets very warm, even under idle. With rising ambient temperatures this could also be the culprit. I would highly recommend installing the Noctua NF-A4x10 FLX on top of the heat sink. If you are up for it replace the thermal compound with something better. Mine was dried up and flaky. I used a small cable tie to hold the fan in place, but others are using screws (image is not from a M1015, but results are pretty much the same) : I leave it running at full speed, it is rather quiet and the heat sink is cool to the touch, even under load. Try the cables first, as suggested by @johnnie.black, but maybe also consider installing the fan.

Just wanted to also credit you for the help, ofc I am aware of the fierce competition in the unRaid docker landscape... I usually also fall back to MC, but Krusader is proving very useful in conjunction with unassigned devices for backups/images I create of machines outside my network. Additionally, MC needs something like screen to work after closing the terminal etc.

Thank you @CHBMB and @binhex, I have set an additional host path and mapped a folder on my cache drive. It seems to be working for now. There is indeed an option to set the temp folder through the Krusader settings, but I think a drive mapping is cleaner. ?

Thank you for your work, @binhex! I played around with the docker and have 3 quesions/issues for now: 1. If I browse a tar archive, it fills up the docker image due to temporary files being created (I presume). Since I also deal with larger files the docker images gets filled up pretty much completely. Is there a way around this? Maybe with another host path? 2. Unraid is mounted via /media. I have changed the mounting point to /mnt/ instead of /mnt/user/ so I can access disk shares. Is the "trash folder" still reliably created in the user shares and not the top level of the disk shares? 3. Is there a better/convenient way to deal with file permissions? I would much prefer to have the option to maintain ownership and permissions of files, especially when creating backups. Thank you!

I am glad you found a solution. I guess your problem was beyond my expertise in the end. Permissions seems to be sensitive with Nextcloud/SQL.

Do you have ONLYOFFICE or other addons installed in Nextcloud? Please enable logging to debug level (0) in Nextcloud and define a logfile location, if not already done, following this: https://docs.nextcloud.com/server/13/admin_manual/configuration_server/logging_configuration.html Post the logfile if possible. Please check the file beforehand for IDs or PWs.

You can see the internal ips in your Docker overview. This is how network bridges are handled in unRaid. I highlighted the one of MariaDB: Please try to edit your config.php as suggested and replace the line of: 'dbhost' => 'ben-server', with 'dbhost' => '192.168.189.24', This at least avoids any issues with Nextcloud having to resolve your domain. If it does not work you can try to add the port also and remove the port from the subsequent line, which leads to: 'dbhost' => '192.168.189.24:3306', 'dbport' => '', Please try this and let me know if it works. P.S.: If unRaid's webinterface is on 444 then, according to your docker overview, Nextcloud is using the same port. If this is so, you have to change one of either.