Kishman

This was my mistake - I didn't read properly - thought the latest I saw was already the stable one. I only brought it up cause things weren't working, so I was trying to see if it will load a different version. I was going to, then just decided to install the docker on my production server - I checked it on my phone and saw the WebConsole. Here's the kicker, I checked today, and saw the same 'blank' page, but I knew it loaded the WebConsole, so I then decided to open it in Edge, and sure enough I saw it. So for whatever reason, my Chrome wasn't just loading it (Version 94.0.4606.61) - however, this doesn't explain why it was opening up to port 8080. Either way, I'm just going to work off my production server now. I see the logs are more closely matching your logs now. This was supposed to be the easy part too... I got a long ways a head of me Thanks for your help - keep up the great work!

Yeah, stopping and starting/refreshing gets rid of that error, but it doesn't seem to take the manual update. The file is fx.tar.xz, I was just shortening it for no reason. Sorry, I meant what I see in my logs. What shows up is so short compared to your logs - yet, I am able to host a server and successfully connect to it, so because of that, I assume it's working. Now I'm at a loss, so not sure how much other things I can change really. This is a fresh install of UnRaid 6.9.2 (on trial version) - not a problem to do a whole fresh install again really...

Ah, my mistake, ok, that makes sense. Did that, getting a e":"No such container: ef1fab5b8f0a"} Stopped and restarted a few times, just continues 'normally' after - does it delete the fx.tar after it updates? Yes - the very first time I installed, it did look like it opened up a WebConsole page (with port 9016), but it was blank - then I deleted everything (docker container, folder, verified it was gone, even deleted the entire docker.img), and started from scratch again but for whatever reason, it tries to load up with port 8080. This server that I'm testing on has just been spun up specifically for FiveM - just want to get the feel of it, then once I do, I'll start to put this on my production server (my production server isn't at my house, so I rather quickly do things locally first). So there's nothing else on this server, except FiveM (then I put on Krusader after to help delete things). Does it go through those loads every time? I thought something was wrong with this loading, but wasn't sure if it was just that simple...

Hey Ich, First off, thanks so much for all your work - seems like you're working around the clock. I'm not the best with knowing how all this works, but I can follow instructions/research where needed. I did try searching through this forum for any info, but wasn't directly related to what I'm having issues with. The issue I'm having is with FiveM. Took me a bit to get it up and now I'm able to actually see my server and load into it. It stated that I'm on an older version and has to revert back. I restarted the docker multiple times to see if it'll pull a newer version, but it says it's up to date. I also set the manual update to 'true' and downloaded the latest fx.tar.xz (4675 as of right now), but I don't think it takes it. According to the other file that's in there, looks like the version is 4394. Anything I'm missing to get this thing updated? On a different note, I can't get the web console working. The first time I got your docker, what looks like a separate terminal window opened up, but I can't do anything in it, just a white page, but now, it opens up to a 'page not found' - I do notice it opens up to port 8080, so I force it to 9016, but same thing. Not sure if this is related if it's out of date or not.