Nodiaque

Hello, Is it normal that since I installed this plugin, everytime the server is rebooted from the UI, it says the server had an unclean reboot and want to parity check? Thank you

Hello everyone, Something is currently using 100% of all my cpu cores and I can't find out what. In ntop, I see >375% on shfs. In my grafana, docker total cpu usage is only 14% from docker, no vm. I also see disk activity around 100mbps. It's usage is so high that I'm unable to play something through emby. I'm on Unraid 6.11.5 servraid-diagnostics-20230318-2302.zip

It's because of the docker. The official docker image does a chmod on startup to its own user. I myself created a openhab user and assigned it the Id of the docker. You can check on the official docker image for doc about that.

Did you check log and post them? Hard diagnose a problem that you can't reproduce. Are you using latest config? Did you check if the templates has changed? There was a lot of change in the last year in swag and other, some are breaking change if you never update your config. The startup log will tell you when you have outdated config and deprecated fonction.

Did you change that file? Cause I don't have that problem at all. My file is in /etc/nginx/conf.d/stream.conf and no problem. This file isn't saved on a mounted drive, it's in the docker and why it's always coming back. I think you have something wrong with your nginx conf. Try starting with a fresh config and work your way down on your modification.

Hello everyone, I'm trying to have qbittorrent working with Swag and Fail2Ban. The reverse proxy work perfectly, but in the log file of qbbittorrent, everything is logged as the docker ip. Thus, all login shows as: WebAPI login failure. Reason: invalid credentials, attempt count: 3, IP: ::ffff:192.168.255.5, username: Hh If I connect directly to the docker, the ip is good. Because of that, I cannot set either "local ip" or fail2ban to work cause it block everyone (since it's the same ip). I tried the original qbittorrent.subfolder.conf, I tried adding these: proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-For $remote_addr; I tried proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-For $remote_addr; I tried proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Host $host; Nothing work

no problem (anymore) on my end with ark (and all others in fact).

I HAVE GOOD NEWS!!!! I just tried something, I though maybe something on my docker is screwing something. I pressed stop all, then started only ark.... and steamcmd started!!! So one of my 60 dockers is doing something weird to steamcmd on certain docker. Starting the investigation now. At least now, I have somewhere to point my arrow! edit: wow, I don't understand anything! I started one by one each container, restarting my ark server each time. Upon starting each container back, all my game server are still working even after a reboot. It's a weird big mystery!

You don't need Br0 to do what you want. But yes, using bridge will work. But unraid doesn't care about your port assignment in the ui (well in fact docker doesn't either). Why? Because all port are open when using Br0. The port won't be reflect on the Gui just like in host mode, reason is the docker can use whatever it wants and you don't have to worry about port assignment. It will show them if they are cooked in the docker template file (which you don't see in unraid) and ich77 already stated he doesn't declare them in the template. But let's say you have Conan exiles and ark server. Both are steam game, which mean both have query port 27015. How would you forward this port to both container? Cannot be done. This mean you need to change the port of one of the 2 game. This mean changing configuration in the server settings outside unraid and for that, you need to check each respective game. This is one of the good reason to not include port in the template. Same goes for the game port. Often, game port are the same for many steam games. 7777 and 7778 TCP and udp are the one most common port. This mean you also need to change the listen port. You need to change that in your game server, either by extra games param for games like ark or through change in server config file. Then, you forward those ports to the corresponding server. BTW, opening each port to a docker network vs your unraid ip doesn't make any security. Why? Because in the end, the packet goes to your unraid server nic anyway since the Br0 is a virtual nic. Opening each port on custom bridge network vs using Br0 is not less secure. You still are forwarding that port in direction of your server nic.

No problem, I know it's not a problem with your container per say. I'm trying to find some docker /unraid guru but so far, everyone is baffled. Specially since while being in your container, I can reach internet no problem! And also since it's also working in debian docker image, a vm and some other docker. If only it was the same result across the board, could at least have something to analyse.

Did you port forward every port? I don't know what other docker you have but you cannot have 2 server on same port even on different internal ip. Even if you route from a different port, the game will want to say hey that's my port, connect to this port. If the ark browser cannot connect, it won't show. There's also a good 10 to 20min delay between server up and seeing it on the browser. I'm probably sure you have a port forwarding issue. Your last screenshot showed 2 ark server, which would cause problem if neither of them use different port. You can check on ark wiki for the port used and how to change them (its not just changing the port in the docker template, ark require extra game param)

I really don't know. All I saw is when I had ark from you installed and then I installed the node, the first layer was already present. When I tried without ark install (was only server), it download the first layer. It might be the debian base since both are debian. I don't know. In the end, it doesn't really matter. It was just something I saw on both container where steamcmd fail vs the one that work.

What I meant by that is both your docker and pterodactyl are using 1 layer that are the same. Maybe it's the debian base, I don't know. But when I downloaded a node for ptero, it downloaded everything except 1 layer. I tried deleting everything from you and ptero, it downloaded all layer. When I tried back with one container from you, it skipped 1 layer. Doesn't mean much, just that these 2 have the same steamcmd error while the other docker I found that simply run steamcmd work no problem. I'm simply trying to wrap my head on what's going on. I know it's not your container that is problematic, I'm just trying to understand what and why.

Br0 won't show you the port mapping. It's like that for everything. Bridge and Br0 are 2 different docker network. Br0 open all port to that ip and you can't change the port.

I'm trying to find the root cause of why steamcmd doesn't work (anymore) for me only on my docker system. I tried pterodactyl and they seem to be using the same base steamcmd as you, so they fail with same error. But looking at this docker, which is a plain steamcmd, it work https://hub.docker.com/r/steamcmd/steamcmd Have any clue of the difference with your steamcmd layer? I tried copying steamcmd from one to another and it still doesn't work. I also stumbed on this (https://steamcommunity.com/discussions/forum/1/3118150513198726419/) but unfortunatly it didn't work either

ok, well soft reboot worked and vm wasn't autostart (few). Problem solved, won't do it again!

Yup, I launch a reboot from the gui, I lost ping 10 sec ago so it seems to be rebooting. I'll wait to see when ping come back else, hard reset

well, array been stopping for the past hours....

ah ok, I though I could kill something from the command line.

good question, I really don't remember. Is there a way to kill the vm process or service?

Hello everyone, As the title says, I created a VM with a dedicated GPU and I forgot I was using this GPU in some docker. When I started the VM, the VM interface froze. I cannot go into VM or into settings ==> vm. I don't remember the name of the vm and vrish list freeze. What can I do to solve that lock? Thank you!

Yup, I even tried with a game I never have. It's really weird.

4 hours when you get the broom? Lol, I think I'm exploring too much. I'm level 21, just got in the map room without the book, have 30% challenge done across the world. I'm 10 hours in lol. I selected proton 7.0.6 in steam, it download proton 7 and now the game start and close, no message, nothing.

Hello, Thanks for the input. If that was the case, it wouldn't work with other steam docker and other unraid. I flushed everything and the problem is still present (I rebuilt all my docker). Thanks!

I've posted it here: