McFex

Hi guys, I'll post this here, becasue I wasn't sure where else to put it. Please move it accordingly - but I was just so excited I found out what the reason for the problem, when the web GUI is sometimes suddenly no longer reachable from anywhere, actually is. If this is already well known, feel free to delerte my post. I am just trying to help, but don't have the time to go through thousands of docs, because I am flesh and blood and old :D Is there a solution? Not really, in the sense of fixing the root of the problem on why it happens anyways, but at least we know now how to get the WebGui live again without having to restart the whole server :)! I searched but mainly found a lot of "ERROR 500" posts, which did not fit my problem. And I did not like those workarounds anyways, so I decided to dig into it with the help of AI, and I [well, actually "IT" did ;)] found out the following (Yes, the following is written by the AI which found out, what's actually going on): Fix for Unraid WebGUI randomly going offline (ERR_CONNECTION_REFUSED) — without rebooting Like many of you, I've been dealing with the classic Unraid WebGUI going down with ERR_CONNECTION_REFUSED on port 8005 — seemingly at random, sometimes after hours, sometimes after days. The only known fix was always a full server reboot. Until now. What's actually happening Unraid's built-in nginx (the WebGUI web server) occasionally dies silently. The process either crashes or loses its PID file, so it can't recover itself. Everything else on the server stays up fine — Docker, VMs, your data — only the management interface is gone. The recovery command (no reboot needed!) If you have SSH access, just run: ``` /etc/rc.d/rc.nginx start ``` That's it. Unraid ships with rc.nginx which has a proper start command that rebuilds the SSL config, cleans up stale sockets, and starts nginx fresh. Within seconds port 8005 is back up. Even better: a watchdog to prevent it ever bothering you again Create /usr/local/sbin/nginx-watchdog.sh: ```bash #!/bin/bash LOG="/var/log/nginx-watchdog.log" if ss -tlnp | grep -q ":8005"; then exit 0 fi echo "$(date '+%Y-%m-%d %H:%M:%S') [WATCHDOG] nginx down — restarting..." >> $LOG /etc/rc.d/rc.nginx start >> $LOG 2>&1 sleep 3 if ss -tlnp | grep -q ":8005"; then echo "$(date '+%Y-%m-%d %H:%M:%S') [WATCHDOG] nginx recovered." >> $LOG else echo "$(date '+%Y-%m-%d %H:%M:%S') [WATCHDOG] ERROR: failed to restart!" >> $LOG fi ``` Make it executable: chmod +x /usr/local/sbin/nginx-watchdog.sh Then add to your crontab crontab -e): ``` * * * * * /usr/local/sbin/nginx-watchdog.sh ``` To make it survive reboots, add this to /boot/config/go: ```bash (crontab -l 2>/dev/null | grep -v nginx-watchdog; echo '* * * * * /usr/local/sbin/nginx-watchdog.sh') | crontab - ``` Watchdog checks every minute. If nginx dies, it's back up within 60 seconds, automatically, without touching anything else on your server. I've been running this since this morning and it's already recovered once. The log at /var/log/nginx-watchdog.log gives you a history of every incident. Hope this helps someone — I know the "just reboot" answer gets old fast. — Bob --- Thank you Bob, now I, McFex, will take over again. So that's it. When the Gui went down, I asked to investigate and that's what it came back with. The next disconnect will show if it works. Time will tell. And I really don't give a shit about anyones opinion about AI, so lets keep this post clean of that, Just take the fix ;) Maybe it is even the root cause for the 500 ERROR, I don't know. But what I know is that server constellations and, combined with that, the Nginx configurations are so different that the problem has never occurred in a broader form, but only with special use cases.

NICE! That seems to be the solution, thank you! Blocklist is now consistent.

HI there. Thanks for this - works great out of the box. Almost ;). I'd like to make my gravity.db persistent. Which folder would I have to map in the unraid docker setup?

THIS IS A RANT! This post is one high top example for a useless and absolut unnecessary post. Yeay, the headline is changed to ******SOLVED****** in big fat letters - but HOW it was solved is missing. Thank you, dear OP, for leaving behind some hope for people with the same problem just to smash it right away, when they come here to find you did not bother to explain what, how and when. RANT END. Now for the more conciliatory part: In all the forums you seek and often even get help the common sense is (and frankly the least you can do for getting help for free) to post the solution in the end, so the people who might have the same problem in the future have a better chance to find an answer. So maybe you can find it in you to tell me (who does have the exact same problem) how it was resolved? Thank you in advance, McFex

Also, eigentlich war ich mir sicher, ich hatte vor meinem Post extra nochmal recherchiert, muss aber gestehen, dass ich bei den Ergebnissen nicht darauf geachet habe, ob die von vor oder nach der Reform waren. Es fühlt sich für mich einfach so dermaßen flasch an, dass ich jedesmal wenn ich es sehe darüber nachdenken muss - kleiner Psycho halt :D. Du hast aber recht, ich habe grade nochmal im Duden meiner Mutter geschaut, die ist da immer aktuell. Auf deutsch heißt es in der Literatur "Stopp". Jetzt könnte man natürlich darüber streiten, dass der Server im Grunde ja eine Maschine ist, und von daher auf dem Stopp-Knopf ruhig auch "Stop" stehen könnte, worauf man dann erwiedern könnte, dass es ja aber darum geht, eine deutsche Übersetzung für die Bezeichnungen zu finden und endlos diskutieren - aber so wichtig ist es mir dann doch nicht - mein Psycho-Hirn wird sich schon dran gewöhnen. Oder ich kehre einfach zur englischen Sprachversion zurück, was ja auch nicht ganz unklug ist, da limetechs Muttersprache (und eigentlich auch die der Computerwelt) ja quasi englisch ist ;)

Moin Moin, Mir ist ein Fehler in der deutschen Übersetzung aufgefallen. Ich habe die betreffende Stelle auf Github gesucht, aber leider finde ich den Eintrag nicht: Im Main Tab (Übersetzt mit START) gibt es im unteren Bereich einen Button, der die Arrey stoppt. Der muss "Stop" heißen - und NICHT "Stopp". Nur, wenn man jemanden auffordert, etwas zu stoppen, schreibt man das Wort mit doppel-p: z.B. den Ausruf "Stopp!" . Auf Schildern (z.B. im Strassenverkehr oder an Maschinen) muss es korrekt "Stop" mit nur einem p heißen. Ich habe lange gezögert, weil ich mir kleinlich vorkam, aber letztendlich ist es einfach falsch (und macht mich verrückt 🤪, aber da bin ich halt ein wenig psycho...) Aber der erste Grund sollte ja ausreichend sein, um das bei Gelegenheit mal zu korrigieren

Hi guys - joining the party Same issue here, too. Still on unraid 6.8.3, pulling latest image or complete reinstall did not work. [13Mar2021 22:37:22.522] ain/INFO] [net.minecraftforge.fml.loading.FixSSL/CORE]: Added Lets Encrypt root certificates as additional trust [13Mar2021 22:37:22.809] ain/INFO] ixin/]: SpongePowered MIXIN Subsystem Version=0.8.2 Source=file:/config/mineos/games/servers/createmod/libraries/org/spongepowered/mixin/0.8.2/mixin-0.8.2.jar Service=ModLauncher Env=SERVER [13Mar2021 22:37:24.192] ain/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release [13Mar2021 22:37:24.481] ain/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release [13Mar2021 22:37:24.521] ain/INFO] [STDERR/]: [jdk.nashorn.api.scripting.NashornScriptEngine:<init>:143]: Warning: Nashorn engine is planned to be removed from a future JDK release [13Mar2021 22:37:27.468] ain/INFO] [cpw.mods.modlauncher.LaunchServiceHandler/MODLAUNCHER]: Launching target 'fmlserver' with arguments [--gameDir, ., nogui] [13Mar2021 22:37:53.927] odloading-worker-2/INFO] [net.minecraftforge.common.ForgeMod/FORGEMOD]: Forge mod loading, version 36.0.58, for MC 1.16.5 with MCP 20210115.111550 [13Mar2021 22:37:53.962] odloading-worker-2/INFO] [net.minecraftforge.common.MinecraftForge/FORGE]: MinecraftForge v36.0.58 Initialized [13Mar2021 22:37:57.050] [Forge Version Check/INFO] [net.minecraftforge.fml.VersionChecker/]: [forge] Starting version check at https://files.minecraftforge.net/maven/net/minecraftforge/forge/promotions_slim.json [13Mar2021 22:37:59.377] [Forge Version Check/INFO] [net.minecraftforge.fml.VersionChecker/]: [forge] Found status: BETA Current: 36.0.58 Target: 36.0.58 [13Mar2021 22:38:07.765] ain/ERROR] [net.minecraft.world.gen.settings.DimensionGeneratorSettings/]: No key layers in MapLike[{}]; No key structures in MapLike[{}]; Not a registry ops [13Mar2021 22:38:08.031] ain/INFO] [com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService/]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD' [13Mar2021 22:38:08.335] ain/FATAL] [net.minecraft.server.Main/]: Failed to start the minecraft server java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted at net.minecraft.world.storage.SaveFormat.<init>(SaveFormat.java:77) ~[?:?] at net.minecraft.world.storage.SaveFormat.func_237269_a_(SaveFormat.java:85) ~[?:?] at net.minecraft.server.Main.main(Main.java:115) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at net.minecraftforge.fml.loading.FMLServerLaunchProvider.lambda$launchService$0(FMLServerLaunchProvider.java:51) ~[forge-1.16.5-36.0.58.jar:36.0] at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) odlauncher-8.0.9.jar:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) odlauncher-8.0.9.jar:?] at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) odlauncher-8.0.9.jar:?] at cpw.mods.modlauncher.Launcher.run(Launcher.java:82) odlauncher-8.0.9.jar:?] at cpw.mods.modlauncher.Launcher.main(Launcher.java:66) odlauncher-8.0.9.jar:?] at net.minecraftforge.server.ServerMain$Runner.runLauncher(ServerMain.java:63) [forge-1.16.5-36.0.58.jar:?] at net.minecraftforge.server.ServerMain$Runner.access$100(ServerMain.java:60) [forge-1.16.5-36.0.58.jar:?] at net.minecraftforge.server.ServerMain.main(ServerMain.java:57) [forge-1.16.5-36.0.58.jar:?] Caused by: java.nio.file.FileSystemException: .: Operation not permitted at sun.nio.fs.UnixException.translateToIOException(UnixException.java:100) ~[?:?] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) ~[?:?] at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:860) ~[?:?] at net.minecraft.world.storage.SaveFormat.<init>(SaveFormat.java:75) ~[?:?] ... 15 more Unraid log says exactly the same as in CmdrKeen's post. MineOS starts fine, though. WebUI is also reachable. Logging in as nobody/my password works fine. Everything seems fine until I want to startup a server. Then the log says the above. In my case it's a forge server latest version I am trying to start. *UPDATE: Applying Docker in "Privileged" mode seems to work.

Thank you, I'll try the VNC solution and also mapping another directory for import/export.

Hi, I'm in the process of setting up your thinderbird docker and have some questions: How can I open links in mails on my local machine (the computer I use to connect to thunderbird via noVNC webUI)? I know I could copy and paste the link, but I would prefer that they open when I click them. Is that possible? How would I import contacts or calendars?

+1 from me. This would be awesome and very helpful for working with shares you download to but because you also need them to be present in PLEX for example and have them on the arrey to be safe and them being bigger in size than 1 TB (meaning bigger than your cache drive) and additionally you want to work with TinyMediaManager on them you set those shares to "Use cache: Yes". A progress bar would be VERY helpful in this usecase! Any news on that? Will we get this in 6.9?

Hey there, Thank you for your Dockers, especially TinyMediaManager. Unfortunately I have some problems with it and I don't know how to solve them. It looks ok, when I scrape a movie - I get the pictures and metadate in the UI and everything seems fine (I can browse pictures and replace them manually, etc, meaning working in the UI is fine). But it doesn't seem to download anything into my movie's folder - for trailers there is at least an error popping up. This is what the log says: Does anyone know what is going on and how I can get TMM to actually download the scraped data? Edit: I set the share TMM works in to use cache (cache=yes) instead to cache=only. So it downloaded the changes/pics/etc. to the cache and the mover would move them to the arrey, which is not really efficient in production. Stupid me - sorry, my bad.

Hmm, I'm sorry I didn't think of it earlier, since I stumbled upon this a while ago and then forgot. https://docs.linuxserver.io/general/swag pretty much explains it all..., more or less . I haven't understood everything yet, but I'm on my way there... I have more questions, but I'm gonna ask them on discord. Thank you 👍

Well, the site says: "...if only IPv4 is detected, then your ISP doesn't provide Dual-Stack yet". But I am not sure, if that means you are also not on DS-Lite. Dual-Stack and DS-Lite are NOT the same, btw: Dual-Stack means you are reachable from the internet via IPv6 and IPv4. DS-Lite means that you are NOT reachable from the internet via IPv4, because several users share one public IPv4 which then gets tunnelled through the IPv6 network of the provider to the different users. A better way to find out is to check in your router settings or write a quick mail to your provider.

Hey CryPt00n, thanks for sharing - I'll try that. My DNS is already setup, since I used to run swag on unraid. So there is no need for setting up an extra network in unraid? Why? (As I said, I want to learn )

The question which makes this post relevant in this forum is further down in bold. Hi guys and CryPt00n, I have kind of a similar setup as CryPt00n here (I quoted him mainly to connect the posts, since we might be on a similar way). Except it's not an SBC, but a Fujitsu I want to have as kind of a gate-server between router and unRaid server. I installed Cent OS 7 and on it docker and docker-compose. I am aware I'll have to open the ports on the centos firewall. Now I need to know how my docker-compose file would have to look like. I tried to translate the docker setup from unraid into a docker-compose.yml file: version: '2.1' services: swag: image: ghcr.io/linuxserver/swag container_name: swag cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=1000 - TZ=Europe/Berlin - URL=mydomain.com - SUBDOMAINS=www,flexcloud,sonarr,radarr,hydra2,sabnzbd,tautulli,minecraft,documentserver,galacticraft - VALIDATION=http - EMAIL=my@email volumes: - /proxyflex/config:/config - /proxyflex/www:/config/www ports: - 443:443 - 80:80 restart: unless-stopped Is something missing? I also can't figure out what exactly my proxy_conf files would have to look like. Let's take nextcloud, for example: server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*; include /config/nginx/ssl.conf; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; <= put unraid server IP there?* proxy_max_temp_file_size 2048m; } } Could someone be so kind and tell me the correct configuration? For example what is the correct resolver IP if I host the swag container on the Fujitsu? * Which IP to put there? Unraid official IP? Or the IP unraid has in the network created by swag on the Fujitsu? How would I find that out? Or not unraid's IP at all but the nextcloud container's on unraid? I understand that the swag container and the other docker containers supposed to use the reverse proxy have to be in the network created by swag. How would I do that in unraid with an external swag installation? Simply check the networks on the Fujitsu and assign the corresponding IPs to the dockers on the unraid server in the docker setups? Or would I create the same network in unraid? How would I do that? I am fairly new to linux and unraid and docker, but I want to learn. I tried to be as clear as possible about my needs and hope someone will help me. Thank you in advance and cheers