Open kylerhenry opened 2 years ago
It looks like the backup docker is stopped every time this error comes up, but perhaps it's stopped until the next backup iteration time?
Edit: This isn't the case; no backup was created at the specified time I tried adding a RCON_PASSWORD: entry to the server (thinking maybe the default wasn't being populated) but that didn't help either.
In the minecraft
container logs can you locate lines that look like this:
[13:39:42] [Server thread/INFO]: Starting remote control listener
[13:39:42] [Server thread/INFO]: Thread RCON Listener started
[13:39:42] [Server thread/INFO]: RCON running on 0.0.0.0:25575
@itzg Negative:
That would explain why the backup container can't connect with rcon. The modpack must be interfering somehow.
I ended up just writing a bash script to do the backups for me since I don't really want to deal with tracking down a bug in over 300 mods in the pack.
Just adding my issue and solution here; if you are using a modpack that provides you with a server download, rcon may be disabled by default. You can enable it on line 12 of server.properties
Just adding my issue and solution here; if you are using a modpack that provides you with a server download, rcon may be disabled by default. You can enable it on line 12 of
server.properties
Thanks, it's so simple I'm so stupid. for paper server the same.
I'm using the following compose file:
And receiving the following error:
Running on headless Ubuntu. I've tried looking at some of the other bug reports here with similar issues, but I can't seem to figure this one out. Is this expected since I'm specifying
tar
mode?