wcg66

I recently moved to this version of the Crafty Controller container since the other version from the arcadiatechnology repository stopped working after the most recent update. I was able to import my server from the former installation so all is good now. I was wondering if anyone else ran into this issue?

Exactly my experience, I got the VM working and started the OpenCore setup and realized I had installed Catalina and not Big Sur. I went back and checked all the settings and I had selected Big Sur all along. After deleting everything and starting over, I could never get Big Sur installed. I appreciate the effort put into this, of course, but something funky is going on making this installation harder to get working than a more manual process.

That did the trick! Thanks!

Thanks for the follow up. I've had no troubles until now and I appreciate the effort!

File "/usr/local/lib/python3.6/dist-packages/unmanic/libs/unmodels/migrations.py", line 53, in __init__ self.router = Router(database=database, migrate_dir=config['MIGRATIONS_DIR']) KeyError: 'MIGRATIONS_DIR' After the latest update I'm getting this error. I can't connect to the web UI anymore. Any ideas?

@dkerlee, I'm running the ROCK software on the NUC. It's Linux based and setup very much like an appliance. The NUC I have is a few years old (5th generation mobile i5 processor with 8 GB RAM) but it seems to be ok. Even with DSP and transcoding it keeps up. I decided to use a 2 TB drive I had lying around as external storage for the library. That works well too and I can access it through Samba (it's also mounted in unRAID too.) Not a bad solution in the end. However, I had the hardware laying around so it was $0 and gave me a use for a NUC I bought

Update: I've moved my Roon server over to an Intel NUC. I've had the NUC for awhile, (I got a good deal a few years ago on Ebay) but never had much use for it. I decided to give it a try and it works flawlessly so far. However, backing up and restoring my library wasn't flawless but it's up and running. This solution only makes sense because I had the hardware and was a simple experiment versus trying to debug random Roon server crashes. No more disconnects from Roon even with the exact same network setup.

@dkerlee I actually restarted the container with --dns 8.8.8.8 which should override any other settings (at least that's what I understand.) I didn't see any difference. I will try removing the PiHole altogether to make sure it isn't somehow messing with the network discovery protocol used by Roon.

@dkerlee I'm watching the logs on the Roon server side and there are all sorts of issues it seems (or perhaps I'm reading too much into the steady stream of info.) There's definitely some network issue which could be PiHole releated but I lost connection to Tidal and my Roon bridge also seem to hiccup a few times. This is all relatively new issues after using Roon for two years or so. I doubt the container is the culprit but you never know. I was getting the same issues on the previous one.

Ok, so I moved to the new container and I moved my Pi Hole implementation to an actual external Pi and I'm still getting random disconnects. It almost seems like Roon is crashing? Has anyone seen this? Stacktrace: at <unknown> <0xffffffff> Stacktrace: at <unknown> <0xffffffff> Error Error Initializing Started Initializing Started Not responding aac_fixed decoder found, checking libavcodec version... has mp3float: 1, aac_fixed: 0 Running This is the log from the container just as it crashes. This is a restart, correct? EDIT: Looking at the logs in the container itself shows a new log starting at the time of the crash. The previous log just terminates with no error. Hmmm. Any thoughts?

I should actually do this. I have three Pi's but two are setup for music streaming, ironically as Roon bridges . I also have an R7000 but it's used as an access point. I will have to eliminate the Pi Hole from the system to verify that's the cause (current as a unRAID VM with fixed IP address.)

I can confirm that moving to this container from the ronch version works fine. I installed and restored from the most recent backup and everything is there. I'll update if I continue to see disconnections (which are most likely unrelated to changing containers, right? EDIT: I can confirm that this version disconnects as well. At least I'm on more current Docker image.

If you can let me know what the settings are when you've figured it out, I'll give it a try. I'm running my Pi Hole on a small VM due to issues I had with the containers not getting the correct DNS settings. It works fine for everything else it seems but it might be related to the Roon issues. I will experiment with turning it off and see if Roon behaves. I see disconnects quite regularly - the Roon UI suddenly goes blank and you get connection message so it's noticeable even in the background.

Thanks. I'll give it (new container) a try, I can keep the other container stopped for now. The connectivity problems are recent and the only thing I can think of is my recent addition of a Pi Hole to the network. However, I don't see DNS requests being rejected specifically. I've looked on the Room community site and they seem to point fingers at various network setups interfering with the multicast it uses. I will also try setting the DNS to something other than the Pi Hole to see if that helps.

I've been using the Roon docker image from the ronch repository. This seems to have disappeared now. Can I move to this new version without losing everything? Can I take a Roon backup and restore it in the new container? I am also tempted to just move to a VM. I'm having intermittent disconnections from the core and like others have noted above, updates wipe out all my settings and metadata.

I'll give this a try, thanks. UPDATE: Turning off validate is key to keeping serverconfig.xml from being wiped out. I can change the server settings now. Seems to be working, thanks.

Validate was "true" does this wipe out the serverconfig.xml? Serverconfig is set to this file. So are you saying, I can't move over a save of our world we have been playing in over to the this container?

Server name, password, save file, the usual settings.

I've seen this question asked before but I still can't seem to figure this out: I'm running a 7 Days to Die server and I'm trying to change the settings in the /mnt/appdata/7dtd/serverconfig.xml file. Whenever this is edited, any changes are overwritten by a new default file when the docker is restarted. What is the correct way to change the server settings for this docker?

Haven't tried anything else yet. I set up an Amazon Glacier account, I'll try that.

No, unfortunately it doesn't save these settings. I get the same result after restarting the container.

It's strange but there's nothing in the logs to indicate an issue. The application hangs when finishing the backup plan setup (pressing the done button on the dialog.)

No, it just hangs. I also noticed one of the CPU cores was pegged at 100% after doing this and stops when you stop the Cloudberry container. I did a test with rclone and I was able connect to Backblaze and upload files.

I think the problem was a) the "+" in the key name or b) I was using an application and not a master key like I thought. I generated a new key on BackBlaze and that connected. However, I'm trying to backup a single file now and it seems to be hung when I press "Done" on the plan config. There's a small window with "Exec edit plan command" open. Note: I'm not sure if this is the issue others are dealing with. If you use an application key you need to use the key ID as the "account" ID not your normal Backblaze account ID. I haven't tried this, however.

Are there any special ports required to be forwarded at the router level? I'm having trouble getting Cloudberry to authenticate both my Backblaze B2 and Amazon Glacier account. I can authenticate using the desktop app on Windows working on the same subnet and Internet connection. (I used the Blackblaze "master application key" when attempting to authenticate.) I am running unRaid as a ESXi VM. unRaid is able to connect to the internet, I was able to get and install trial key and download apps, etc. I think the issue may have been a "+" in my master key. I generated a new key with no symbols in it. I can authorize and connect now.