• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About upthetoon

  • Rank


  • Gender

Recent Profile Visitors

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

  1. I think an old port fwd rule I had in exposed it. I was using a weak password on the deluge front end too. I’ve since removed the forwarding rule and changed to a more complex password too.
  2. Just to update, I think this has originated from a malicious Deluge plugin. -rw-rw-rw- 1 nobody users 22041 Dec 27 17:45 booster-0.2-py2.7.egg
  3. Ok, thanks. I’d only restarted a day or two ago when the .1 came out.
  4. Hmm. So without something dodgy installed I should have been safe? That’s a worry then.
  5. That's the full list. 1&2 - Letsencrypt 3 - Sabnzbd 4 - Deluge 5 - Another torrent docker I dont use anymore 6 - Wireguard I've since deleted the torrent entries. Does leaving a FWD entry to a port that isnt in use on the internal side create a security risk?
  6. Is that what that forwarding rule does? I've always had a blindspot for network configuration... I set that 80 > 85 port forward up as letsencrypt runs on port 85 (and 448)
  7. These are the port forwarding rules I have. The miner was running under the user "nobody" which I use for applications.
  8. Hi, I noticed CPU activity at 100% this morning and "xmrig" was running. A quick search and there are a couple of other threads of this happening to others who have opened some of their ports. I've had reverse proxy set up for a good while but I don't think I have any ports open directly to the server. I've attached my diagnosis file if anyone can see anything suspicious that would be much appreciated. ridcully-diagnostics-20210312-0812.zip
  9. Last check completed on Fri 07 Aug 2020 08:24:00 AM BST (today), finding 0 errors. Duration: 1 day, 10 hours, 53 minutes, 4 seconds. Average speed: 111.5 MB/sec Looks like parity wasn't valid. That's a slight worry, not sure how that happened. Better than a hardware problem though...
  10. Yes, I've changed that setting now, thanks. Not sure why I had it like that in the first place. 25% through, no errors found on this new run...
  11. Hi, My server had a problem booting up last week (the CPU fan wasn't spinning). I had a second machine being used as a PC so swapped all the drives into that and it booted up fine into unraid and everything seemed good. A parity check has now completed and its come back with over 700k errors. This was a scheduled check with had "Write corrections to parity disk" set to "yes". I'm now thinking that was a mistake... I've kicked off a second check (which won't write corrections). Attached are the diagnostics. Advice appreciated... ridcully-di
  12. I don't have the experience to help you (I went the easy path and got a nvidia shield so no 4k transcoding needed), but if you want someone to spend their own time to actually help you, I'd edit that response and take out all the whining.
  13. Happy birthday Unraid. I just checked and it's been 10 years since I built my server. It's only just had its guts replaced this year. I love how solid Unraid is now.
  14. Thanks for the comments. I upgraded to a Ryzen 2600 at the weekend with a MSI x470 board. After an initial hiccup (I forgot to check about integrated graphics and couldn't boot it without a GPU - £5 later from a friendly local repair shop I was in business with a "WinFast PX7600GS") it all went smoothly. Unraid keying off drive serial numbers works like magic, swap out MOBO, CPU, RAM add a GPU and it boots straight up and in with the same config as before. I've then been on eBay and flashed a H310 Dell SAS card to IT mode last night to replace