Freshavakado

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Freshavakado

  • Rank
    Member

Recent Profile Visitors

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

  1. Thanks for the information, that's really good to know, always appreciate learning something new. So I did try it again with the correct commands while using SteamCacheBundle console and I'm still now seeing anything happening after entering the command. I thought maybe some screen caps might help explain a bit. So that's what the console looks like when I put in the command, I tried it twice and the rest of the photos are how I have the container set up. I really appreciate your help.
  2. This is what I'm getting when I type that into the SteamCacheBundle console.
  3. I've been setting up SteamCacheBundle on UnRaid 6.6.2 and I have been following this guide https://squishedmooo.com/the-new-and-easier-all-in-one-steamcache/ but I've not been able to get past the part where it says to "Run the following command in an SSH session to your unRAID server: docker exec -it SteamCacheBundle tail -f /data/logs/access.log". I've typed it in on the server itself, I've used the remote terminal from the UnRaid dashboard, and I've downloaded PuTTY and tryed to do it that way and I've had no luck. I'll type it in and nothing else will happen. I'm still fairly new to U
  4. An update to the MineOS issues, I was able to start the server running 1.12.2 but anything that is 1.13 or newer won't allow the server to start, I'm going to try to contact @hernandito about this to see if they have any idea as to what the problem may be.
  5. That's good to know, I didn't even think the problem could've originated there. Thanks again for the help!
  6. It did fix that issue and it makes a lot more sense now, all the settings stay after rebooting the docker container now unlike previously. I'm just looking around forums now to see why it won't start after I followed a couple tutorials. It seems to be an issue with accepting the EULA but I cannot find where the eula.txt file is nor have any idea where the server root is.
  7. Thank you both, the reboot fixed it and there is no longer any warning message from Fix Common Problems, just having issue with starting the Minecraft Server on MineOS but that is problem for another discussion thread. Thank you very much for your help.
  8. I guess my question is if neither of the paths fix the issue, what is the problem then? I may not have explained myself well enough. The first one was what it defaulted to, the second is what I also tried and that didn't work either. Refering to the Host Path that is, which is what I believe I'm supposed to be looking at.
  9. I just checked, the only docker container I have at the moment is MineOS and I tried the Host Path both of these ways and neither got rid of the problem (or the issues I'm having with starting the Minecraft Server with MineOS).
  10. Okay, I checked my Docker settings and it was setup to /mnt/user/appdata and I changed it to /mnt/cache/appdata then back again to /mnt/user/appdata and for both the error still came up. Anything else I could be missing?
  11. I've been using the plugin Fix Common Problems and it recently came up with the error listed in the title. I'm still very new to UnRaid and I'm not sure what the issue is or how to fix it. Anyone know how to fix this issue and if its a problem or not. Thanks!
  12. I've tried to do that but then when I go to delete the files I get a File Explorer warning that I need permission to make changes but I'm logged in under root.
  13. I created a share that I no longer want on my unraid server but it has files that I cannot delete. How can I delete this share?