Kudjo

Members
  • Posts

    23
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Kudjo's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Similar to XisoP, but I'm not coming from old build. I'm currently running 1.21.1.3876 (which is current, at time of posting) and running "check for updates" doesn't change the "not available" message. I've also tried restarting the docker image; no luck. I'm just about out of ideas. Do any of you fine folks have a suggestion I can try?
  2. I'm helping someone with this too (a dirty shutdown made his two SSDs in his cache pool become unmountable). Did you ever figure out what to do about the "Error mkdiring" message? (JorgeB is correct, it is not creating the folders, but we're running the command as root with no luck.) Any ideas?
  3. When you provide us with an excellent build, I turn around and serve it to a dozen others who are ITCHING to play on the new update. All I'm saying is this is kind of your fault for making this work so well. ;P I'll tell them to cool their jets and wait a few hours. Thanks again.
  4. +1 If possible, I don't mind doing it on my own so you're not bothered. Thank you for building this! I've been using it for MONTHS with no problems at all.
  5. I did remember to delete that directory after trying to reinstall it once or twice. When I finally remembered, I deleted the directory and tried again from scratch and got the log that I posted earlier. (I'll repost it from my most recent attempt from a minute ago). I don't know if this helps, but I noticed that when it runs altitude.sh, it temporarily creates a directory called: "altitude.sh.xxx.dir" where xxx is equal to some number. I can see it start to unpack to the freshly created directory, but then it deletes that directory. So, all I'm left with is "appdata\altitude\altitude.sh" Yours installs properly after "Unpacking JRE ..." I'm on unraid 6.8 rc4. Did they make a change that I should be aware of? What should I do next? I'm happy to help.
  6. I removed (and deleted the image) of the Altitude docker and when I reinstalled, I keep getting this in the log: Does anyone have any ideas on what I should do about it? The only other thing that changed is I am now running unraid 6.8 rc4. Thanks again for all you do.
  7. Also, if anyone cares, you can use the game's included "server_configurator.exe" to make your own Server config file (called: "launcher_config.xml") which you can then load into the appdata location on ich777's Docker build. Just overwrite the one that's already there and all of YOUR settings are what the Docker loads on the next restart.
  8. It worked! Thank you so much! I was surprised how quick that was. And it was SO easy to setup! If anyone wants to try it, feel free to hop onto "Kudjo's Altitude Server" and let me know how it goes. Thanks again!
  9. ich777, Thank you so much for your great game server builds! I use several of them. Is it possible to get one working on unraid for Altitude (Free on Steam and off steam)? Pretty please? I got it up and running following their instructions but immediately thought of you and your excellent work on other games. Links: Altitude on Steam Link Altitude developer page for linux server files and instructions What do you think? Again, THANK YOU for you superb efforts!
  10. I hadn't understood the difference. Thank you for clearly explaining how all that works. That new knowledge, mixed with your instructions got me up and running as desired. Thank you very much!!!
  11. This was highly informative. Thank you. Okay, I'll go in order. 1) I didn't know that was specific for 1.14, thank you for telling me that. I don't remember seeing that requirement, so I'm glad I know now. Are there any other times when that variable should be applied? 2) You're absolutely correct, I'm missing the rest of the tag in that screenshot (I pinky promise I've used the correct tag before). Unfortunately, the tag: "1.15.1.791-8bec0f76c-ls11" still doesn't do the trick for me. Plex is still reporting that it's on version 1.15.2.793. I'm getting my tags from: https://hub.docker.com/r/linuxserver/plex/tags if there's somewhere else I should be looking up the tags then maybe that's my problem; incorrect tag names. 3) I'm basing my experience off of the official Plex Inc Docker container. It reported the Tag number I had selected as the version, so I assumed it worked the same for the LinuxServer Container. So, thank you for teaching me that doesn't seem to be the case for this one. Any ideas of what to try now?
  12. No change... I added the variable, as you suggested. But I must be missing something. No matter what I try, the "version" still reports as "latest" and the Plex container still says I'm running 1.15.2.793. Could someone please point out what I'm missing/doing wrong? I'd love to have this control again. Thanks.
  13. I am having this EXACT same problem. Trying to rollback because I sometimes can't leave the Plex home screen. (I can still play everything if I click it directly and search still works, but plex will never leave the home screen). The TAG/Version method has worked before, but it won't roll back this time. I'm also running Unraid Version 6.6.7. The official Plex docker rolls back like normal using the same TAG method, so I wonder if there might be a hangup with this build in particular? Does anyone have any suggestions?
  14. I was literally restarting my server after updating to 6.6.5 when I wrote that. I didn't see that the 6.6.5 notes mentioned "dropboxes" so I assumed that nothing changed there. But now that I read the notes more carefully, I see that the Black and White theme have the arrows displayed again. I'll read a bit more carefully next time. Sorry 'bout that. Thank you for a quick response.
  15. Love the product and I'm a fan of the choice you give to your users. Keep it up!