dnLL

Members
  • Content Count

    172
  • Joined

  • Last visited

Community Reputation

5 Neutral

About dnLL

  • Rank
    Member

Recent Profile Visitors

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

  1. For what it's worth I just decided to upgrade to Python3. So I uninstalled Python2, pip works fine with Python3, just had to update some other scripts I was using that weren't fully compatible with Python3 but I'm glad I made the switch.
  2. I have python2 and pip installed, however... root@server:~# pip install docker -bash: /usr/bin/pip: /usr/bin/python3: bad interpreter: No such file or directory root@server:~# python -m pip /usr/bin/python: No module named pip Somehow pip is looking for Python3, which I don't have installed. If I install it well, it works but for Python3, I need pip for Python2. I noticed there is a pip3 command as well, not sure why the default pip command isn't configured correctly.
  3. I'm happy to hear about this. I will wait for the stable version, hopefully soon. Sent from my Pixel 3 using Tapatalk
  4. I'm having the same issue of high disk writes on btrs cache with dockers. This seems to be very well known... My SSDs are are 35 days old, my server didn't do much (the mover barely moves anything) and yet, 25 TBW on both SSDs. They're 500G SSDs, so that's 50x their size in a month with a server idling 99.999% of the time. Insane.
  5. I noticed the docker doesn't ping anymore now that it's in a different subnet. I can access the webUI just fine, but pings don't work. I see the ICMP requests go through my pfSense, just no reply from the docker. It works with dockers that are in the same subnet as the host, and it also works for VMs that are in that specific separate subnet (which is a separate VLAN). Networking is so complicated. Trying to fix the ping issue for my monitoring server... eh... EDIT: it's only THIS specific docker that has the issue. And pings work fine if I disable VPN. So I guess it ha
  6. Just got it working without editing the routing table. I just edited the docker settings instead, enabling br0.2, then selected br0.2 for the qbittorrentvpn docker and changed the IP to 10.1.2.54 and done. It's now sharing that other dedicated VLAN with the developer VM. It would probably be a better idea for me to put it in its completely separate VLAN but that will do for now, as I would need to shut down all the VMs/shares to edit the network settings and I can't do that right now (hosting some semi-important stuff). Thanks for your help by the way, happy you immediately found t
  7. I'm still learning when it comes to networking (I started this pfSense project from scratch), what I currently have is my LAN network on 10.1.1.0/24 and I have a couple of VLANs on different /24 subnets. All of my "safe" LAN devices (such as my desktop, my server and most of its VMs and dockers) are in that same subnet. In Unraid, I have eth0 with "VLAN number" set to 2 because I have one VM using br0.2 instead of br0. That VM is in its own separate VLAN. When it comes to the routing table however, I only have what I consider to be the default settings: Not
  8. Ah, and why is that? It works with the other containers. I guess I'm just going to put it in a separate VLAN then. What if I change the lan network to a smaller subnet? I'm not using the default bridge because it's easier for me to monitor the docker when it has a different IP address than the server (I use CheckMK to monitor) and also because I would have other dockers trying to be on port 8080 which would be a problem as well (since most templates aren't designed to modify that setting even when it's there).
  9. I disabled the rule just to be safe. It didn't fix the issue. I guess I'm gonna run some wireshark diag next...
  10. FWIW 10.1.1.54 responds to ping. Here are the screenshots requested, I removed the user/pass again: https://imgur.com/a/ccdLClH
  11. If I put ENABLE_VPN to false, webUI works. Which made me think it isn't a firewall issue. I don't have a pi-hole, I do use pfSense however as my router (and pfBlocker-NG is disabled). 10.1.1.54 and 10.1.1.102 are in the same VLAN so they don't go through pfSense at all, shouldn't be a firewall issue (especially considering it works with VPN disabled in the docker settings). However, the DNS settings... I am really not sure of as I do have a rule that redirects all the trafic on port 53 to pfSense itself.
  12. Right. So I installed new gen, it did fix the error, in fact I have no error at all anymore in my log... but the webUI won't work from local network (trying to access 10.1.1.54:8080 from 10.1.1.102). Here is the full log, with user/pass removed: https://hastebin.com/yorasuyoxe.swift
  13. This docker has been a source of frustration forever because of my inhability to make the VPN part of it working. I gave up multiple times in the past but would like to try again and make it work this time. So, installed the docker from scratch... I added the crt, perm and ovpn files from PIA in the /config/openvpn folder. I tried Toronto and Montreal, both supporting port forwarding. The docker template settings I have: Network Type: br0 Fixed IP: 10.1.1.54 Privileged: On Host Ports: all default VPN_ENABLED: yes VPN_PROV: pia STRICT_
  14. Worked perfectly for me with a X11SCH-LN4F motherboard, didn't even have to reboot and no need to edit syslinux.cfg. pfsense VM immediately recognized both ports (be careful to use i440fx, if you use Q35, the ports will only be detected if they have active connections which is not exactly what we want for pfSense). Haven't rebooted yet, unsure if Unraid will try to take the ports for itself, if so I'll do some syslinux.cfg magic but don't think that will be necessary at this point.
  15. Sorry if it's already been discussed (couldn't find in the original post) but my motherboard has 4 Intel I210 controllers each with their separate port, with lspci -n I see this: 02:00.0 0200: 8086:1533 (rev 03) 03:00.0 0200: 8086:1533 (rev 03) 04:00.0 0200: 8086:1533 (rev 03) 05:00.0 0200: 8086:1533 (rev 03) Now, adding 8086:1533 to my syslinux.cfg, will Unraid still be able to use the first 2 ports (0200 and 0300, which I'm curently using in bond0) while I'd like to passthrough 0400 and 0500 to a pfSense VM?