caseyparsons

Oh, I didn't realize I was looking at the tags for the wrong version. But got it now. Thanks! Unfortunately, my son likes to play on his amazon fire tablet sometimes and wants to be able to use his PC other times, but I guess I'm gathering that the two clients can't coexist on a server.

Oh. So on his tablet he can connect to this server, but to play from his PC he has to connect to a different server? Well that stinks. But thank you for the reply!

Oops, you're right. Thanks for pointing me to the right thread. I re-posted over there.

Sorry for the noob question. Current server version is 1.19.10-beta20. My son's PC client version is 1.19.0. When he tries to log in, he gets the error "Could not connect: outdated client!". How do I specify a server version that matches his client version? How do you keep these in sync? I saw this tags page so I tried to input 1.19-01 as part of the repo. So I entered "binhex/arch-minecraftbedrockserver:1.19-01" as the repository, but then the docker fails. I get this error in the Update Container page: "docker: Error response from daemon: manifest for binhex/arch-minecraftbedrockserver:1.19-01 not found: manifest unknown: manifest unknown." Is my syntax wrong? Is this not the right way to specify a specific version? I searched (a bunch) for the answers but just couldn't find what I needed. Thanks! Or should I not be using Bedrock version?

Sorry for the noob question. Current server version is 1.19.10-beta20. My son's PC client version is 1.19.0. When he tries to log in, he gets the error "Could not connect: outdated client!". How do I specify a server version that matches his client version? How do you keep these in sync? I saw this tags page so I tried to input 1.19-01 as part of the repo. So I entered "binhex/arch-minecraftbedrockserver:1.19-01" as the repository, but then the docker fails. I get this error in the Update Container page: "docker: Error response from daemon: manifest for binhex/arch-minecraftbedrockserver:1.19-01 not found: manifest unknown: manifest unknown." Is my syntax wrong? Is this not the right way to specify a specific version? I searched (a bunch) for the answers but just couldn't find what I needed. Thanks!

Well look at that. I needed to REBOOT. After the reboot the server started responding to network on the port that I was not originally connected to. Yep, I had some stuff passed through for plex. Already working on cleaning all that up, but I can handle. Thank you for the help! Really appreciate it.

OK good call on this. The motherboard actually has two integrated NICs. One is a 1Gb and one is 2.5Gb. I was only cabled to the 1Gb, but am now cabled to both - but no improvement yet. Thanks for the idea.

Hi friends, I've been very happy with my unraid server for many years. Today I upgraded my motherboard to the MSI B560 Torpedo, CPU to i5-11400, and new RAM. These replaced a Ryzen 5 1500af and GTX 960 GPU. After fiddling with the UEFI boot settings in the BIOS I can finally get unRaid to boot but not get to a good running state. I get all the way through the scrolling loading stuff and to the login prompt. The server states that the IPv4 address is 192.168.10.10, which is what I had previously configured in the GUI. However, the server is not available on the network. I can't ping to it, and I can't ping out of it from the console. It will ping itself, but nothing outside the NIC. I tried to boot into GUI (and safe mode with GUI) but the GUI never loads, I just get a flashing cursor. I do see some modprobe errors, which I assume temp sensor errors because I switched CPU and no longer using nvidia, but all those plugins are still installed. I figured I would clean that up after, but hopefully not causing the error. What can I try now? Attached is a diagnostics file that I initiated from console then pulled off the USB. For some reason the date says yesterday but I definitely ran it today. Thank you! tower-diagnostics-20211220-2324.zip

Hmm I tried this but didn't work for me. Just got new errors. This seems to be the important part: {"t":{"$date":"2021-02-18T12:35:47.675-05:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}

Having the same problem after update.

Is this docker container still being maintained? I enjoy using it, but can't be running an unmaintained container without security patches.

The utility is showing all of my disks except for one. On the right side at the top it says "1 new drive detected. (sdb)", which is the drive that is missing. I have re-scanned controllers multiple times but it keeps showing the same. The missing drive (sdb) is a WD Red 3TB WDC_WD30EFRX-68EUZN0. I have three of this identical drive and it's finding the others, just not this one. The missing drive is seen in the array, storaing data, no errors, passing SMART, and appears healthy. I have six drives plugged into the motherboad sata ports, including the one missing sbd. I also have a PCI sata card with 1 drive that is showing up fine.

I just bought the Corsair CX Series 600 Watt (available in 430, 500, 600, or 750 watts) for my desktop (non-unraid) and it works awesome. The modular design is so good for cable management, makes the whole case look nicer. Big upgrade for me.