DazedAndConfused

I figured it out, thanks. Not sure how I can see what the autostart order of my dockers is, but after randomly shuffling stuff around, the icon turned green.

I have not seen where Im able to change the order of the folders. I cant drag and drop them.

I really dont understand the autostart checker. How is this supposed to work? Explain like im 5, please. I created my folders but the icon is red. How the heck am I supposed to arrange the folders to pass this check?

The Satisfactory docker does not allow you to properly setup a dedicated server on the experimental branch. According to the wiki, you need to set "-beta experimental" in Steam CD. Please see the link here If you add this to the "game parameters" on the docker, nothing happens. I think its not working because "-beta experimental" needs to be passed in during the "update server" portion of your script for this docker echo "---Update Server---" if [ "${USERNAME}" == "" ]; then if [ "${VALIDATE}" == "true" ]; then echo "---Validating installation---" ${STEAMCMD_DIR}/steamcmd.sh \ +force_install_dir ${SERVER_DIR} \ +login anonymous \ +app_update ${GAME_ID} validate \ +quit else ${STEAMCMD_DIR}/steamcmd.sh \ +force_install_dir ${SERVER_DIR} \ +login anonymous \ +app_update ${GAME_ID} \ +quit fi -beta experimental needs to be able to be passed into the code block above as a configurable option. I have tested running the dedicated server locally through steam on my gaming PC and it works perfectly on experimental. Its impossible to get the docker server running on experimental for me right now.

Merry Christmas! Just made the switch a few days ago and I believe I chose the same settings. However, my first backup using v3 is currently running and its saving the backups in seperate .tar files per docker container. On v3, I just got a single .tar file with the whole backup. Is there a benefit to having it do the backup like this or did I choose the wrong setting during setup? I do my backups on the 25th of every month at 3AM, for some reason, Plex is taking HOURS and is holding up the process. 😅 Just wanted to ask Thank you so much for maintaining this feature.

Thank you for this fork. Just got rid of Invitarr.

How does Google Drive work with this now. I am no longer able to authorize my RClone token via the Webgui. It just gives a 404 error. Google had been sending emails for months about them deprecation something involving 0Auth and I think that affected Rclone. Does anyone have any info I can look at to get it going again?

Having the same issue as above.

I would like to switch over to the dev branch since the auth functionality with organizr got broken with the latest updates. How do I achieve this with this docker?

These are bugs related to the game, not the container. There is a bugtracker for satisfactory where people have already reported the issues you are seeing. You may want to play on Update 4 in Multiplayer if you dont want to deal with Update 5 (experimental branch) being extremely buggy right now. @ich777 I saw your question about the -multihome thing I posted and the answer is....probably. They released some patch notes today saying they fixed whatever the issue was that caused the Linux based servers to stop working after the IPV6 implementation. Ill remove the -multihome option and update my server later and let you know if it works with the new changes the devs made.

Thats my fault, I said extra parameters first when I meant game parameters. Im glad you've got it working

Yes, under "game parameters" in the docker, just add "-multihome=0.0.0.0". For whatever reason your error is reading in the parameter as "ultihome=0.0.0.0". I have no idea why its reading "-m" as an argument and missing the rest of it.

Just FYI, the new 5.0.6 update for Satisfactory borks the server, it will not start. Its been reported on their bug tracker already, so avoid restarting your server until they issue a new patch. Satisfactory Q&A (satisfactorygame.com) EDIT: NEVERMIND. ISSUE IS FIXED WITH -multihome=0.0.0.0 in the docker settings under "game parameters". Add this to fix your servers! Issue was caused by CoffeeStain adding IPV6 support

Thank you for the advice. I will test it out when I get home.

Probably a dumb question, but how do I configure the container to use a custom domain? Do I just put it in the address field in the docker?

*deleted* Edit: ACTUALLY!! Just saw this update from Coffee Stain. They actually cite the wiki article I linked you earlier. So it actually is more functional now. State of Dedicated Servers in Satisfactory - https://www.youtube.com/watch?v=Nn-1s87JJxc

Is a docker for Satisfactory possible? I can buy you a beer for your efforts For reference: Dedicated servers - Official Satisfactory Wiki (fandom.com)

You are probably having issues because Sickgear has not been updated for the new changes with Qbittorent. I no longer use that program as I've moved to Medusa since the Sickrage/Sickgear drama...but thats my best guess as to why 4.2.0 doesnt work for you.

Thanks for the instructions on rolling back to 4.1.9. 4.2.0 has not been whitelisted on several private trackers and probably wont be for a least a month for some.

Thanks for the tip! I totally misunderstood what this was. I got it setup on my main PC and I was able to make a python script to remove the dead torrents

Binhex, would you be able to implement qbittorrent-api? At the moment, you are unable to identify torrents that have been removed by a tracker. You have to manually go through each torrent to see whats going on with it. Other clients just put those torrents in an error status but qbittorent does not. I have asked on their github and was told that using the api would allow me to use scripts to run operations on the client like removing dead torrents.

Any idea if this docker has support for the qbittorent web API? (https://pypi.org/project/qbittorrent-api/) I'm asking because I would like to try and run API calls to delete torrents that have been marked as "Unregistered" on the private trackers I'm on. For some reason, QT does not have native support for this and you have to use a script to remove these torrents.

Im having constant issues with the docker bringing my server to a crawl. Im migrating from qbittorent and it seems like everything I do in rtorrent maxes out my CPU utilization on my server and locks up the server. I've had to force reboot twice already. Simple things like deleting dead torrents that have been removed from trackers or force rechecking files so that I can get everything migrated is causing the server to be at 100% CPU most of the time. Ive never had this problem before installing this docker. In order to keep this from completely killing my server, I run operations on 5 torrents at a time and even still, I have issues with that. Does anyone know what may be causing this? I'm going to have to disable this docker until I find out why this is happening.

Hi Uriel, looks like the main repo is inactive now. Someone forked the project and have been actively adding updates at https://github.com/barbequesauce/Watcher3 How do I go about switching the docker over to this repo? Or is that someone you need to do on your end?

Hey guys, My cache drive started acting up tonight and all of my dockers kept crashing. The drive says that it mounted as read only and I dont know what to do. I would like to try and recover as much data from the drive as possible. Unfortunately, when I run the reiserfsck, I get the following error: reiserfsck --check /dev/sdi1 reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/sdi1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted I am not sure how to proceed as I dont really understand the instructions this is giving me. I would like to be able to copy whatever is salvageable to a new drive but I am unable to do any operations on this drive due to it being read only. I have attached a syslog as well. I would appreciate any help! tower-syslog-20191030-0511.zip