KillahPwnz

This worked perfectly! Thanks so much! @ich777

-Not sure about the world reset bug. I'll have to look into that. -Password is 5+ chars I did try restoring from a backup an hour prior and that didn't work. I was playing the game an hour before the issue without issue. Leading up the boot loop, I found an article that aimed at improving the lag in valheim. This one was specific to a valheim dll within the server and client. Increasing the bit rate of data flow by 4x by modifying the dll in dnspy. When I made the changes and saw the server wasn't able to start up, I restored my backup dll (original) and still faced the same problem. At one point, the container was complaining about Valheim+ being enabled, it said to disable and try again in the logs. I disabled it and that didn't help. Had never seen that before.

@ich777 Hey, I'm stuck on a loop when trying to start my Valheim container. Have you seen this? I was trying to console into the container to check the directory /serverdata/... , but it keeps booting me from the shell when it loops. TIA

Has anyone had issues with Valheim where all of a sudden no one is able to open doors/chests out of nowhere when playing with other people? It started happening yesterday, no issues before that. I had my friend leave the server to test it, sure enough, I could open doors/chests the MOMENT they disconnected. Another thing to note, my server doesn't show up on the community list for them - it does show up for me. So I've had my friend connecting via IP ever since that became an issue. Thoughts? TIA Update: It seems this is a lag/desync issue and the Valheim devs are working with Steam on a fix.

Not with SF. I will try disabling restart first.

Sorry for the trouble. I will disable the restart of the container at backups which should fix it.

Hey, I'm still getting the same errors after the container's been down for ~20 mins for backup. Catalysm noticed this in the start script: "the appendonly file is stored in /var/lib/redis and not in ${DATA_DIR}. Could be the reason why the data isnt persisted still"

Hey @ich777 My CSMM-7DTD container had issues reconnecting to discord after the container was down for 23 minutes this morning for an appdata backup. I was talking with Catalysm, he believes this is due to the start-server script not explicitly setting the redis server to --appendonly on start. Is this something you can change on your end? I can't find this start script in appdata. He linked this yaml for ref: https://github.com/CatalysmsServerManager/7-days-to-die-server-manager/blob/master/docker-compose.yml#L47-L48

I didn't do anything differently for the web server (allocs) in the config. Just pointing my domain to the CSMM container. I couldn't figure out how to get the web server behind swag as well since it's the same domain I'm using (my own). Kept popping up with "duplicate errors" when I'd try to create two .conf files for the same domain, or when I'd try to add both configs to the same conf. i.e. Config A: point CSMM Container to my domain | Config B: point 7DTD Container (hosting the web server) to my domain.

Hey, yes, your container. I was able to get it to work by forwarding the web server port at the router. Otherwise, I wasn't able to connect to the live map. I was hoping to get the live map to work with swag for SSL, but I couldn't get that piece going. The CSMM server is behind SSL though. Not sure if it's because I have two different network types (one for reverse proxy containers, and the other bridged. Swag and my CSMM container are on the proxy network type and the 7DTD server is bridged.

Setting up CSMM on 7DTD server - Do I need to add the web server port that Alloc's creates to the Container page? (i.e. TCP4 - Allocs, Container Port:#) I have Alloc's installed on the server and working, created the webtoken to be able to add the server to CSMM. However, I can't resolve serverip:webserverport and adding the server to CSMM fails. Thoughts?

Steam oauth was down for a while - working now!

@ich777 Hey, I downloaded and setup your CSMM 7dtd container with reverse proxy pointing to my domain. I believe I have all that setup correctly as I have no issues hitting the CSMM homepage from both Unraid and externally via the web. However, when I click "Get Started" to get connected with Steam I get the following error. Have you seen this before? I wonder if it's actually down for maintenance or it's something else since it's my first time setting this up. Thanks for any help. Edit1: I don't see anything in the CSMM logs that point to anything wrong, only that it's trying to redirect to /sdtdserver/addserver since I'm not logged in. Edit2: Looks like from Googling, steam has maintenance every Tuesday. I'll wait!

Got it to work by specifying '-beta alphaXX.X' (xx.x version # desired) in the GAME_ID field (tacked at the end) after reading some past comments.

I've tried removing the container with image and redownloading, it still seems to pull the latest beta 19.3 (not 19.2)

The output_log doesn't show the playername or Steam ID like it did in the previous stable version:

Here's the error that pops up each time I or anyone tries to connect

Anyone know how to roll back a beta version of 7DTD? I put in -beta latest_experimental in the game ID and it seemed to update fine, but I nor anyone else can connect to the server and I want to roll back for the time being. I tried removing the -beta tag to see if it'd pick up the latest public release and it didn't. Thanks!

Downloads started working out of nowhere - I swear I did nothing lol Separate issue with Sonarr now - thanks for the replies!

Yeah I've tried several endpoints and the logs don't seem to show anything wrong.

Just tried Ubuntu iso which is well seeded as you mentioned. Seemed to start strong, then dropped to 0 KiB/s.

Couldn't find much on deluge forums - only that people had success switching to QBitTorrent. I switched to QBitTorrent (by binhex) and I'm getting the same result. The torrent(s) is added to the client, then almost immediately drops to 0 KiB/s after starting (upon container reboot). I'm at a loss here, not sure what else I can try. Keep in mind, everything worked fine just a few days ago.

Tried switching to wireguard, same result. Disks look good on space. Not sure on trackers. I'm going to check out the deluge forums to see if anyone is experiencing anything similar.

Q22 complete and still can't connect properly. I've tried several servers across various countries. Currently on romania with config: client dev tun proto udp remote ro.privacy.network 1198 remote nl-amsterdam.privacy.network 1198 remote uk-manchester.privacy.network 1198 remote ca-vancouver.privacy.network 1198 remote ca-montreal.privacy.network 1198 remote ca-toronto.privacy.network 1198 remote ca-ontario.privacy.network 1198 resolv-retry infinite nobind persist-key cipher aes-256-gcm ncp-disable auth sha1 tls-client remote-cert-tls server It seems to connect, webui works, downloads start, then drop to 0 KiB/s quickly. This behavior is the same after each deluge reboot, no matter what I change it seems. Any ideas?

so I did all of the above with the fallback option, ncp-disable, etc., and still can't get it working. I can connect to the Web UI, where I see the downloads start upon docker restart, but then the downloads fall to 0 kb/s quickly. It does this no matter what changes I make. Disabling the VPN fixes the issue (obviously). I've also tried switching the client to wireguard (new feature) to no avail. Not sure what to do at this point. Binhex-delugevpn v2.0.4.dev38 PIA with active subscription