I_TheRenegade_I

I shall have to look into that! It's a starting point! Thanks! I'll do some research tonight while at work. Quick google says I can install WireGuard on a firestick, but it needs some extra steps, which is what I expected and have no issues with! I'll post more info as I progress, thanks for the suggestion. It's exactly what I was looking for.. I was just hitting a wall with my terrible wording on google searches...

Hi all, I am lost and really struggling here. I have had UnRaid for a number of years and have a nice collection of media I use Emby for viewing at home. I have wanted to access it from outside my home, but have had a hell of a time getting Emby/UnRaid to allow connections from outside my home network. I have a dynamic IP, but have used DuckDNS to get a SSL cert and still can't seem to get connections from outside my home. I have forwarded ports and everything, and have had numerous game servers running, so I am really guessing it has to do with SSL and DuckDNS and that crap. So I have given up on that I feel the next best way to is install a VPN on my server and then on my Firestick and then boom! It'll appear as on my home network...right? But what VPN docker should I use that would also have a Android client?? All my google searches always lead to VPN for firestick for IPTV, downloading, etc. Looking for just something to connect a Firestick to my home network from outside my home. Long winded I know, sorry.. guidance would be greatly appreciated.

Hey @stevep94 I'm having this same issue, just wondering if you found an answer here or on Discord? Thanks

Is there any easy way to run a Forge server in MineOS? Can't figure it out for the life of me.... There are some specific mods that are Forge only that my son would like to have,....

So, looking for some help. The WebUI has suddenly deciding to refuse to connect. I had to change to port 8444 (but its been that way since the start). All my other dockers I can connect too, its literally just mineos and the WebUI. Just refuses to connect. Scratch this, for some reason the config file in the appdata file didn't take the 8444 port, which is weird as it was working before on 8444. Unfi-Controller uses 8443 as well. So, I have had it different for over a month. Regardless, changing the port in the config file in appdata seems to have the Web-UI back and running

Yup, same here. I have mine set to run the 1st Monday of the month, and its been running for 14 hours now. Was supposed to stop after 8 (at 8am) Maybe the plugin hates February?

THANK YOU! I've spent hours on this stupid thing.... Lord knows if I've screwed anything else up....

OK, then how do I get krusader to run as root. As there are files I need to move back into the Mine-OS directory for plugins to work, and I can't because I don't have permissions... I've tried adding a password, forwarding port 6080, and when I try to change to root mode, it says my root password is incorrect...

I've having an issue I can't figure out. So I moved some files around to make my minecraft server a little less full of plugin files that make the mineos webUI stupid slow and a huge resource hog, and the owners on some files have changed from nobody/users to root/root. I can't for the life of me change owners back to nobody/users and now cannot move files to get the server back up and running. I can't get krusader to log in as root, forwarded port 6080, tried added the password in the set-up. Just tells me the root password is wrong. Tried using commands in console to change the permissions on the dirs/files, no luck.... Help?

Ditto. I have a 6 core 12 thread server with 64gb of ram and over the past 2 or so weeks when I try to save or backup the server the usage will spike to 75-90% usage on all cores/threads for about 10 min. Something has changed, it takes so long to load the mineos web UI and crushes system resources trying to do anything with the server via the web ui... That is when it loads... it refuses connection for 10-15 min after starting the docker....

OK, I am seriously confused here, and really need some guidance and/or direction. I can't seem to find guides that help me out, so I am losing my mind. I have an UnRaid server with 2 onboard NICs (eth0 is my home network and eth1 goes to my neighbors network) and a PCI 4 port NIC (none active for anything atm, but I had it in my last server, so it came over) So, this particular server hardware is new to me about a month ago, ditched the old salvaged desktop and went to a server I got via friend (Supermicro X9SRW-F, Intel® Xeon® CPU E5-1650, 64 GB DDR3 Multi-bit ECC, case. Drives, SAS controller, 4 NIC came from previous server) Dockers - EmbyServer, binhex-krusader, unifi-controller, binhex-mineos-node VMs - Win10, but not running atm and don't even really need it. Was thinking of game servers originally. OK, on to my issue(s), with my new beefier hardware, I figured I could be a good Dad and uncle and set up a MineCraft server for my kids and nieces/nephews. Both the MineOS docker and the Unifi Controller use port 8443, so I can't have them on the IP. I have bridged my eth0 (by itself) and now have br0 from which I understood I could have IPs set per docker, but when I try to use br0 when I set up a docker, I cannot assign an IP to it. It tells me its outside the subnet and the installation fails. I am sure I am just missing one or two settings, but I can't for the life of me find where I am going wrong.

The only docker I am running is Emby. And no VMs. I guess it must be a hardware issue... that's what I was worried about...

My bad, I thought I had attached it with the diagnostics... syslog-192.168.0.110 crash.txt

Anyone have any ideas?

OK, I am back. I ran memtest for 3 days and had no errors, and it has been running fine until I tried to access it today (been working tons) and it was offline. Box is powered on, ethernet is still active, but I cannot access the server remotely, and when I turn on the attached monitor, its a black screen. the last line in the saved log is Sep 22 08:21:59 MediaServer root: issuing standby command Then it goes through the boot sequence as I hard to do a hard power reset. I have no idea where to go from here. I have also attached my diagnostics as @trurl suggested. I was waiting to see if it happened again and have some logs before brining this thread back to life. Hardware issue? Software? Any ideas? mediaserver-diagnostics-20200928-1445.zip syslog-192.168.0.110 crash.txt

I will give this a shot and see what happens. Also I found a few more threads talking about doing memtests, so I'll do that as well.

This has happened twice in the past 2 weeks (or so), the server goes offline, doesn't appear on my network, can't ping it, can't login, and when I turn on the monitor I have attached to it just shows a plain old blank black screen. First time I just rebooted and went about my day (wrote it off to a storm we had earlier), it just did it again last night (Saturday) and I had to do a hard shutdown and I have left it off, hoping to fiddle with it tomorrow (Monday) when I work the night shift. Where's the best place to start to see if this is hardware related or if Unraid itself is hanging? I understand that logs are stored in the ram, so having to do a hard shutdown won't keep any logs... Server has regularly been on for months at a time and not had an issue, this seems to be a new thing I get to deal with.... Help?

Current cache is btrfs.

So I managed to get a sweet sweet deal on a pair of brand new Samsung 860 EVO 500GB SSDs. So I am going to replace my really old crappy 2 tb HDD that is currently my cache, and I am wondering if I should put both SSDs in and set them up in a Raid 0, or if I should put them both in and have one as cache and one as the app data/backup drive for the USB. Or, am I completely stupid and can 100% live with just a single 500GB as cache/app data. I'm not running any crazy amount of dockers/VMs, but I am also going to be upgrading my server to a quad core i7, so I'll probably play around a bit more with VMs. Thoughts? And as a side note, whats the best/easiest way to upgrade a cache drive without losing any docker settings?

Awesome, thanks both of you. Great info!!! I appreciate the help!

SO I am changing out my parity to a WD Red 8TB. I'm in the final stages of preclear, I just want to make sure I have this right. After it's done, I just stop the array, unassign the current parity (6TB Cuda), assign the new WD Red to the parity and then let parity rebuild. Correct? After the parity is done rebuilding, I can format the existing parity drive and add it to the array. Any point in keeping it for a bit? Preclear on the Red is all clear and perfect. So no concerns there. Parity check was done Monday of last week. So the current parity is good and up to date. So to be clear, am I right with thinking the following steps are correct - Wait for preclear to be done - Shut down array, unassign current parity, assign new parity and let it rebuild - Format existing parity and add into array as another disk - Have more space and enjoy my new larger array Right?

Sorry, went away again for a couple weeks. What I have ended up doing is disabling the NFS shares and connecting to the server via IP rather than name. Haven't had an issue since doing those two things (i did them at the same time, so can't say exactly what fixed it). So hopefully things stay working. Thanks for you help, weird problem for sure! Mod could close/mark as solved if they want.

Name of the share is "Media" To connect to the share I am just adding the network location in windows... \\Server\Share I haven't had any issues until recently, so I don't think it's a windows thing. Could it somehow be file permissions? I'm totally lost and confused. mediaserver-diagnostics-20190809-1635.zip

So it is in fact NOT working. I tried to move a 60GB directory and it's telling me that I need 40GB more space on the array. Tried deleting the config file again, does not work. Any further suggestions?

Sorry, had to go away for work for a week. It seems to be working now. But I only had the one batch of >20GB to move. I'll get another batch to move and try again to have more than a single attempt at writing.