Jump to content

physikal

Members
  • Posts

    62
  • Joined

  • Last visited

Posts posted by physikal

  1. 1 minute ago, jordanmw said:

    Geoblocking is not a good solution- they bounce off of plenty of other places once they find a target.  I often found colleges in the US that had been exploited, that were turned on when I cut off their russia IPs.

    yeah I 100% agree it's not a long term solution. Just to buy me some time while I investigate and rebuild some VM's that could be compromised.

  2. 1 minute ago, nuhll said:

    again, if the connection would come from the qnap, then the ip of the qnap would stand there.

     

    Its a direct connection from outside into unraid.

    I thought so as well.  What's odd is the 50.106.16.89 address was an old address I had from my ISP, and when I checked my fw I saw 1 active session on port 6895 to an Amazon IP (Assuming AWS).

  3. 36 minutes ago, jordanmw said:

    check your exposed ports:  https://www.grc.com/x/ne.dll?bh0bkyd2

     

    If you don't find any- that means that something is exploited within your network.  Do you have a microtik or qnap device anywhere?  Those were exploited en masse recently by a russia hacking group.

    yes I do have a QNAP device actually.  I'll check that out I guess.  I've turned on geoblocking on my fw for the time being.

  4. I'm seeing this in my system logs:

     

    Jan 14 00:23:31 Tower nginx: 2019/01/14 00:23:31 [error] 4984#4984: *1158237 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:31 Tower nginx: 2019/01/14 00:23:31 [error] 4984#4984: *1158237 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:33 Tower nginx: 2019/01/14 00:23:33 [error] 4984#4984: *1158248 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:33 Tower nginx: 2019/01/14 00:23:33 [error] 4984#4984: *1158248 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:34 Tower nginx: 2019/01/14 00:23:34 [error] 4984#4984: *1158255 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:35 Tower nginx: 2019/01/14 00:23:35 [error] 4984#4984: *1158255 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:35 Tower nginx: 2019/01/14 00:23:35 [error] 4984#4984: *1158261 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:37 Tower nginx: 2019/01/14 00:23:37 [error] 4984#4984: *1158261 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:39 Tower nginx: 2019/01/14 00:23:39 [error] 4984#4984: *1158275 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:39 Tower nginx: 2019/01/14 00:23:39 [error] 4984#4984: *1158275 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"
    Jan 14 00:23:40 Tower nginx: 2019/01/14 00:23:40 [error] 4984#4984: *1158278 user "admin" was not found in "/etc/nginx/htpasswd", client: 188.243.58.117, server: , request: "GET /Main HTTP/1.1", host: "50.106.16.89", referrer: "http://50.106.16.89/"

    What's interesting is I'm 99% sure my unRAID box is not externally accessible.  So that concerns me.

     

    Any ideas on this?

  5. I was previously on 6.5 and I had no issues with my VM's when Parity check would kick off, now every time parity kicks off I get alerts from software that is running on the VM non-stop the entire time parity check is running (~20hrs).  The thing that gets me is it shouldn't even be in the parity check since this VM is running directly from an unassigned drive.  I wouldn't think parity check would impact that.

     

    Any thoughts?  Thanks!

  6. I'm looking at DR scenarios and am curious if there is a guide out there on how to backup unraid as well as restore in the event of a flash drive (unraid OS) failure?

     

    Basically if my flash drive that unraid is installed on fails...I don't want to lose all my array config which I would imagine would cause a loss of data....how do I prevent this.  Thanks!

  7. Is there an unRAID app/docker that handles pxe/network boot and install of different operating systems?  I have a few computers in my house, and often help friends out with reformats.  It would be AWESOME if I didn't have to track down my Win10 flash drive every time I wanted to install an OS.  If I could just boot a machine on my network and install over pxe boot that would be slick.  But every guide I've seen is fairly involved.  Is there anything out there where I can just install the app, upload the ISO's, modify the menu a bit, tweak my DHCP server for the pxe boot settings and be off with it?

  8. I have a 24 bay Supermicro box running unRAID.  I have 2x 6TB Parity drives, 6x 6TB and 8x 4TB drives....with 8 more bays available....are 2x 6TB parity drives really going to cover a failure? 

  9. @Jcloud  Just realized you wrote up a node guide.  I noticed you used mkdir as root on the host.  Let me know if you have any problems with that.  When I did that, every node directory I made had host perms that the docker didn't have permissions to, so when trying to run the storjshare load command via docker container it didn't have permissions to load the other nodes outside of the initial load the docker container made.  So check out my step 1.

     

    Just an FYI for when you pimp this thing out :P

  10. 4 minutes ago, Jcloud said:

    Don't have to, but if you want to just go up in the thread to my example of making a node, that address is the eth address I'm using for Storj.

     

    HAHA too late! Before I was on unraid I lost 14.5BTC from a currupted password file, from a failing HD. I've cried many tears over this. ;)

     

    lol, I don't think of it like that.  If I sent you ETH now, I HOPE it goes up for you.  :P

     

    Sorry for your loss.

     

    Use l0rd's ports, he seems to know more about the ports than I do though my current setup is working fine.

×
×
  • Create New...