Kopernikus

Members
  • Posts

    90
  • Joined

  • Last visited

Everything posted by Kopernikus

  1. Hi, Solved it. Settings -> Global Share Settings -> Enable user shares
  2. Hi, Just build new Unraid server, first pre-cleared my hdd's, formatted them, create two cache pools, started array and waited for the parity check to complete. However even after reboot if I go the the docker or VM tab it says failed to start. If I go to the docker/VM settings it says "path does not exist", also appdata --> shouldn't Unraid have created these? Included are my diagnostics, hope someone can help. unraid-server-diagnostics-20210819-0801.zip
  3. Hi, Got almost same question, except I have 2 M2 slots 1 PCIe3 & 1 PCIe4 My use of unraid would be Plex, Pi-Hole, some docker containers, and maybe some VM's to test things. I would buy 2 M2 ssd's, what would be the best setup? Option 1 2 gen3 nvme1 in raid1 Option 2 1 gen4 ssd 1 gen3 ssd If so, wich should be used for what cache purpose?
  4. Hi, Finally decided to ditch my Synology NAS and build an Unraid server. I got an Gigabyte Z590M motherboard / Intel 11700 / 2X16GB RAM in a Node 804 case. For the storage I will reuse my 5 WD Red drives (each 6TB). The only thing left to buy are 1 or 2 Nvme SSD's for the my cache pool. The motherboard has 2 M2 slots, one supporting Pcie 4 and the other Pcie 3 So now my question: Do I buy one Pcie 4? And what size would be fitted for my setup? Or do I buy two to put them in RAID1? If so do i buy 1 Pcie4 and 1 Pcie3? Or better 2 Pcie3? And what size? Thx in advance for the help!
  5. Do you use it with 1 or 2 fans? Also did you replace the stock case fans with aftermarket? Would it make a difference to a buy a double 1Gbps add-in and agragate those two compared to Agregate to build-in and a single 1Gbps add-in?
  6. If I'm gona stick with the motherboard I wanted then 3000Mhz is max (2933 or something), I was thinking to get 2X8GB and if needed adding 2X8GB more, I think in the scenario I will use unraid as file server/media server (plex) and running a few docker containers 32GB will be more then enough or am I wrong? Will the Dark Rock pro 4 fit? If I check partpicker site it says only the Dark rock pro 3 will fit? I have have enough spare external hdd's to move my data, I could do it other ways but I'lll make it to complicated then. Would it be better then to add in another 1Gbps card agregate with the build-in 1Gbps card? Or won't it make a big difference compared 1Gbps to 2Gbps (aggregated)? And you right in the case I upgrade my switch in the future to 10Gbps to buy a fiber DAC.
  7. How many watt would you suggest then for the PSU? I thought of getting Corsair SF450 Platinium 450W (SFX) then What do you use as cooler? I'm not planning any overclock just simpele NAS for media streaming and my dockers. So maybe stock cooler? No direct plans, I was just planning in the future if I upgrade my switch to a 10G switch, also my Synology now is connected with it's two 1Gbps ports aggrated, or do you think 1Gbps compared to 2Gbps aggragted won't make mucht difference?
  8. Hi, At the moment I have a Synology 920+ NAS running with 4 6TB HDD's en two 512GB M2 SSD as cache. The NAS is connected with 2 RJ45 cables to my Ubiquiti switch with link aggregation enabled. I'm using this NAS for file storage and and running docker containers for plex, torrents, vpn, pi-hole, wireguard, etc. However due the lack of proper docker support (outdated kernel) and poor hardware I wanted to swith to Unraid. I have a few question and proposal setup: Fractal design node 804 --> compact case but enough room to fit my 5 disks + 2 M2 Asrock H470M PRO 4 motherboard (6 --> only 5 usable if using both M2 SATA + 2 M2 slots) --> enough SATA & M2 for my needs, possible to expand with add-in cards Intel 10x00/K (still to decide) --> Shoud I go with i5/i7 (think i9 is overkill)? And the K or non K version? But certainly with Quicksync support for Plex Corsair DDR4 CMK16GX4M2B3000C15 8GG (16GB (2) or 32GB (4) --> 16 or 32GB? Corsair RM650, 650 Watt PSU (modular) --> 650W enough? Dark Rock Pro 3/4 CPU cooler or Corsair Hydro Series H100x --> Air cooling or water? System only gona be used as NAS and trascoding no gaming etc. + will Dark Rock 4 fit or stick with 3? Case FANS stock Fractal Design or Silent wings / Corsair AF/SP fans --> Advice regarding case fans, leave the stock ones or replace them? Migrate the 4 HDD's from my NAS + 1 spare (to be used for parity) & the two M2 SSD as cache in raid1 --> HDD still funtioning fine, and using to two M2's as cache Optional ASUS XG-C100C 10Gbps network adapter --> I was thinking of bonding the stock 1Gbps with this card (but lowering 10Gpbs --> 1Gbps) so I can aggregate it to my switch, however if I ever upgrade my siwtch to a 10Gbps I can disable the agregation and use only this card. Or is it better to only use the 1Gbps build-in? Or but an 1Gbps add-in for the aggragation? And last question, shoud I buy a separate GPU? I now it can be used for Plex transcoding, but the CPU also has QuickSync, and the other hand 75% of my streams used direct play since most of the use Nvidia shield who can handle most formats. Any tips and advice welcome 🙂
  9. Hi, I managed to install WireGuard on my Synology NAS (thx to: https://github.com/runfalk/synology-wireguard) All is working to setup a connection to the NAS, however after creating the container I have this error in my supervisord.log: 2020-12-08 19:33:55,806 DEBG 'start-script' stderr output: could not detect a useable init system Any idea? Or maybe still not 100% compatible...
  10. Just did an uname -r got 4.4.59+ so no WireGuard.... Hope they will upgrade soon...
  11. Hi, Would Wireguard also work if I run the docker on my Synology NAS? Because the only WireGuard container I got working was Wireguard-Go, because in the Synology NAS the Wireguard kernel is missing. Thx
  12. Would it be hard to also include Wireguard support for "custom" VPN providers? Did a test this morning with my VPN provider with OpenVPN got 250Mbps with Wireguard got 790Mbps. So the upgrade would be great and port forwarding is also supported and working (at least with TorGuard). Thx!
  13. Don't now what changed but seems to be working now with: NAME_SERVERS=1.1.1.1,8.8.8.8 Tried 100000x..... sorry
  14. Correct if I put NAME_SERVERS=1.1.1.1,8.8.8.8 the container can't connect to the VPN, I get unable to resolve errors When I put NAME_SERVERS=10.10.50.50 without public the container connects to VPN but can't resolve once connection is made (seems logic) When I put NAME_SERVERS=10.10.50.50,1.1.1.1,8.8.8.8 all is working fine without any problems Also one more question, I have setup portforwarding with my VPN provider (TorGuard), do I need to specify the port somewhere in teh eniorement variables of the docker? Thx
  15. I'm not using the hostname of pihole but it's DNS so NAME_SERVERS=10.10.50.50,1.1.1.1,8.8.88 I understand your explanation however as soon as I remove the pihole dns from the name server line, the containers fails to make the VPN connection. As stated before this does not happen to all containers who have VPN connection, with some I can leave the pihole DNS away.
  16. @Binhex Can you have a look at my question above? Thx 🙂 Also expect to do see donation for your great work
  17. --> post moved from DelugeVPN thread On 9/22/2020 at 4:00 PM, binhex said: looks like you have name resolution issues on your host, it cannot resolve the vpn endpoint you are trying to connect to, from your log:- 2020-09-22 15:37:38,948 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error you need to figure out why you cannot do name lookups, most probably firewall related, also i noted you have your network set to '--net='proxynet' i would remove that and set it back to 'bridge' as per normal and see if it connects ok then. @Binhex Found the problem... but need your opnion.. So what I did, made a shell connection to the running container, did a ping to bg.torguard.com --> could net resolve Then did a ping to 89.249.73.170 (ip of bg.torguard.com) --> resolves So since I'm using Pi-Hole as DNS server I set my Pi-Hole DNS in DNS_SERVERS and all was working... except error trying to resolve to google.com etc. To my knowledge it needs my Pi-Hole DNS to setup the connection but once VPN is up it needs an open DNS Then I did NAME_SERVER=pihole dns,1.1.1.1 And now all seems te be working fine. However is there any privacy problem in setting my pihole dns as first dns?(My pihole uses unbound as resolver) And why doesn't this happen to other developer qbittorentvpn container? Maybe somthing with the IPtables config? Also on thing I don't understand, why is the torrent tcp/udp port exposed in the container? This makes no sense to me since this port is only availlable through the VPN. So only webui en privoxy port should be included in the docker or am I wrong?
  18. Hi, Just added the container through sudo docker run... instead of the wizard, same result, also disabled firewall. Where do you see '--net='proxynet' in the log? --> just saw it was in @bigbangus log file not in mine. Could it be an other OpenVPN version ? This docker also seems to work: https://registry.hub.docker.com/r/markusmcnugen/qbittorrentvpn/ I run it wirth exactly the same docker settings as yours.
  19. Hi, Haven't set it to '--net='proxynet' docker was created with the synology docker wizard, if I check it's set to bridge. I will create the container manual and see if that changes, with the other docker and don't have this error, also in the past all worked fine.
  20. Hi, Attached 2 logs 1 with binhex docker other from other developer, both same settings exept binhex docker gives network error. supervisord-binhex.log logother.txt
  21. Same here, the docker image does not resolve anymore, here with Torguard as VPN. Before all was working fine, tried the Qbittorent docker of Binhex also, same result. Tried similar docker from other developer and working... so I gues there must be something wrong. Maybe also worth to note I'm not running my docker images on Unraid but on a Synology NAS.
  22. @binhex Hi, I tried everything, nothing worked (already running this docker for 2 years), then to test switch to your QbittorentVPN docker, still same network error. Then to test tried qbittorenty/deluge docker from other developers and.. working same VPN provider same config... switched back to yours, network error. As I stated the problem began since last update, is there somthing changed in your docker images that could cause this? The others are working but privoxy is not included and I was always happy with you dockers images, so rather use yours... Can I provide or do something so you can test?
  23. @binhex Hi, Would it be possible to integrate Wireguard? Since my VPN provider (Torguard) now supports Wireguard on all their servers including port forwarding. I allready tested it on my pc and all seems to be working fine. For the meantime using OpenVPN, wich is woking fine btw, maybe a nice upgrade for the future. Thx
  24. Hi, I've set log to full & debug. Link to log: https://1drv.ms/u/s!ArQhL4LigQi2j8d3Rq_cvUwTYfqVCw?e=yExRij Thx
  25. Same thing here, container updated overnight (on my Synology NAS through watchtower), it's starting but doesn't work. If I look to the logs I get UDP local not bound + inactivity timeout (UDP link remote is connected). I'll try toi rebuild container and see what happen, otherwise going 1 version back and disable auto-update. Any idea? Update: just found this error: 2020-08-30 05:05:09,268 DEBG 'watchdog-script' stdout output: [info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure... So it's a DNS faillure, but is this local or the DNS used within the VPN?