Gronsak

Yeah it seems like it's just the container stopping/restarting that does it since if I run docker restart Enshrouded_Proton yields the same issue... Does enshrouded support rcon? can't find any documentation around it in my googling. is there another way of doing a safe shutdown?

Figured it out, it was indeed the config file. While it looked fine on visual inspection, if I removed it and re-entered all my settings into a newly generated one it all started working again. The issue seems to have been some kind of corruption occurring when appdata backup ran during the night because it was back the day after. For now I've turned it off for the Enshrouded Container until I have time to do some troubleshooting and implement the propper file whitelist so it only touches the backups and nothing else.

Yeah it's all still there and it all worked the day before and still no luck after a couple of days... The only info I could find refers to adding a Default user group but that didn't make any differens but I'll see if I can find any clarification on their forums

I just set up my server yesterday and it was working perfectly (except refusing to take my save from my co-op world but could work around that). However, today I can't connect to the server any more, just getting this error message in the game even though I'm 100% sure the password is correct and with this log output from the server [I 00:05:31,122] -------------- Session ---------------- [I 00:05:31,122] Machines: [I 00:05:31,122] m#0(128): up 0 (0), down 0 (0), remote 0 (0), limit 256, lost 0, ping 0 ms, EstablishingBaseline [I 00:05:31,122] --------------------------------------- [I 00:05:46,533] [online] Session accepted with peer (steamid:[redacted]) [I 00:05:46,533] [online] Added peer #0 (steamid:[redacted]) [E 00:05:47,114] [online] Begin auth session with peer #0 [I 00:05:48,413] [online] Client '[redacted]' authenticated by steam [W 00:05:48,454] [session] Unable to find machine for peer 0. [W 00:05:48,454] [session] Unable to find machine for peer 0. [W 00:05:48,454] [session] Could not store acknowledge of packet id: 100. [I 00:05:48,485] [online] Disconnecting peer #0 [I 00:05:48,486] [online] Removed peer #0Anyone have any tips? Edit: This issue was caused by the config file getting corrupted in some way by a backup script. Removing the file, letting it generate on server start and then re-entering all the settings fixed the issue temporarily.

For some reason when I try to run tailscale on this container recently it binds on port 443 which stops nginx from starting up, I've used this succesfully up until recently and am a bit unsure about what changed to break this. I did activate HTTPS on tailscale a couple of weeks back but it's been working up until just a day or two ago so don't know if it's related but also tried turning that off again. From what I've understood Tailscale Serve Protocol uses port 443 and while that has been activated before without an issue I've tried to set Tailscale Serve to no but no luck. Anyone has any idea on what to do from here, currently can't get NGINX up and running while using tailscale on the container which breaks my usecase for accessing some stuff when away from home. Edit: I found how to fix the issue As long as this field was populated with a port value it seems like serve is started no matter what you sett Tailscale Serve to. When I set it to blank the issue dissapeared

Yes, currently running 6.8.0 rc7 to see if it fixes the propblem, it did not so far edit: So I got IOWait on all cores which is what's blocking all threads, assigned the docker to only one physical core to try and mitigate the issue

So I've been using this Docker for about two weeks now and I'm running into the problem of extreme CPU usage during multiple episode files import, happens with both manual import or automatic. It basically blocks the CPU from doing anything else while copying the files stopping me from doing anything else with the server. Anyone had similar problems and know how to fix it? (working on getting proper logs for everything but so far I don't really see anything strange in the Sonarr logs, but I'm not an expert, trying to get some data on what's happening on the CPU side)