• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About kreene1987

  • Rank
    Advanced Member


  • Gender
  1. [Support] - Letsencrypt (Nginx)

    yeah I'm out of it today. Sorry.
  2. [Support] - Letsencrypt (Nginx)

    I've thrown a recommendation in the upgrade notes that people change their ports away from 443 and 80 due to the conflict with the new Unraid SSL cert system. Perhaps that will alleviate a lot of the common issues seen above.
  3. I'd recommend adding something about those with LetsEncrypt using port 80 and 443 now conflicting with the new Unraid SSL cert system. Most people are posting over in the nextcloud and LE dockers so perhaps they would see it here first and prep accordingly. Note that port 444 (or 445?) is already reserved for something else so a different port (I used 442) must be used.
  4. New Forum Registration Policy

    Glad to see this implemented! I think it will work great.
  5. I can access my stuff through LetsEncrypt reverse proxy. Are you using that?
  6. [Support] binhex - DelugeVPN

    Yes thank you so much binhex. I'll let you guys know if any further mail shows up, but for now everything seems to be working as expected. Lesson learned: USE the privoxy for your meta gathering apps!
  7. [Support] binhex - DelugeVPN

    I've now incorporated socks5 with auth proxy for all 4 levels
  8. [Support] binhex - DelugeVPN

    See responses above. Thanks for responding so quickly. I suspect the socks might be the issue?
  9. BACK after giving up, couldn't be happier

    Just upgraded to 6.4.0 after 108 days of uptime. So glad I gave this a second chance! Everything is working spectacularly (minus a nastygram from ISP the other day which I've posted about in delugeVPN)!
  10. [Support] binhex - DelugeVPN

    So I just got a nastygram from my ISP, and I'm wondering how in the heck it happened. I shut it down for now but plan to bring this back online. I've confirmed my IP and DNS are not leaking via ipleak, I am getting a good VPN connection per the logs, and I've confirmed via magnet link from ipleak that my external IP matches the logs. Is there anything else that I can do to test for leaks? I'm not entirely sure how it happened. Is there any way to add a killswitch or is this already a part of the build? Wanting to be as safe as possible considering the circumstances. TIA.
  11. [Support] - Letsencrypt (Nginx)

    Me either. I will state that I am using settings, so I'm unsure if this is because I went with a bit different approach?
  12. [Support] - Letsencrypt (Nginx)

    Phew this one is throwing me for a loop. I port forwarded my IP 80 --> 81 and now I can VPN in and get to all of my internal links and everything is working great, but the Unraid GUI connection is refused. Any reason the 2 would be related?
  13. [Support] - Letsencrypt (Nginx)

    I hope someone sees this soon as I basically live out of nextcloud (calendar, documents, etc.) and this has brought this to a screeching halt without VPN'ing into my network! Is there a way to roll back to a previous revision?
  14. [Support] - Letsencrypt (Nginx)

    Mine is dead this morning as well. Same error log as above with different webserver address (clearly).
  15. HELP! Harvey bit me

    He doesn't have the USB though with the original drive mappings using the identifier. Unfortunately you can only NOT have one of the following in single parity: 1) USB drive for unraid 2) Parity Disk 3) Array Disk(s) I believe you are going to have to try to rebuild the lost disk using the "swamp" drives and "swamp" parity, then that disk could be directly implemented in your new installation. Better than starting from scratch at least!

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.