swtz

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

swtz's Achievements

Noob

Noob (1/14)

0

Reputation

  1. That's not the right docker image... I didn't see any of that in logs for the binhex container. Has anyone figured out a way to get usb drives to reliably appear? Only way I've found was to set puid and pgid to 0.
  2. As a complete nextcloud newb, a "data" path would probably make sense in the unraid docker config screen, luckily I'm just testing everything out now lol!
  3. I'm unable to open the webui. The logs look fine like the client is started, but all I get is "unauthorized" in text on the page. Any help? Thanks!
  4. For reference 192.168.1.217 : main pc 192.168.1.6 : unraid server Just got qbittorrent installed, everything appears to be working, but I'm getting a ton of errors in unraid log. Jun 24 14:48:42 Tower nginx: 2019/06/24 14:48:42 [error] 4938#4938: *819467 connect() to unix:/var/tmp/binhex-qbittorrentvpn.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.217, server: , request: "GET /dockerterminal/binhex-qbittorrentvpn/ws HTTP/1.1", upstream: "http://unix:/var/tmp/binhex-qbittorrentvpn.sock:/ws", host: "192.168.1.6" I did have to change the host for the webui from 8080 to 9090 as 8080 was already being used. To do this I deleted the ports that were in the config (the one pointing to 8080), changed the webui container variable to 9090 and created a new TCP port for 9090:9090. Is that the right way? This is happening even when I'm not connected to qbittorrent via a web browser in any fashion. I can post more info if needed. Thanks.
  5. what's the process of rolling back to an older version? I'd like to be pre 2.0 if possible. Thanks!
  6. Hey all, So I was messing with network settings trying to be able to get docker containers to use a different default gateway (i.e. wanted some of them to be able to run through a VPN router). So what I thought would work is adding a vlan on br0 (in the same subnet as mine). I was kind of following this post here: In the process I think I messed something up and want another set of eyes on the situation. I've included my diagnostics. So some of the issues I'm seeing is that I can't connect to the vnc of a vm unless I'm accessing unraid from my backup (secondary nic) Ip address... which is weird. Also, for some reason when creating a new docker container, I don't ever see custom br0.200 (the vlan I created on br0). BUT I can select it when creating a new VM. When I go to the docker settings screen I see the br.200 options for setting up dhcp, but there's no entry in the "gateway" field (even though I have one set on the vlan interface). Here is the info in the "routes" portion: Protocol Route Gateway Metric IPv4 default 192.168.1.1 via br0 1 IPv4 192.168.1.0/24 br0 1 IPv4192.168.1.0/24 br0.200 1 IPv4192.168.1.0/24 bond1 1 IPv6 ::1 lo 256 Anyways, any help is much appreciated. Thanks! tower-diagnostics-20190503-1437.zip
  7. Hey all, So I was messing with network settings trying to be able to get docker containers to use a different default gateway (i.e. wanted some of them to be able to run through a VPN router). So what I thought would work is adding a vlan on br0 (in the same subnet as mine). I was kind of following this post here: In the process I think I messed something up and want another set of eyes on the situation. I've included my diagnostics. So some of the issues I'm seeing is that I can't connect to the vnc of a vm unless I'm accessing unraid from my backup (secondary nic) Ip address... which is weird. Also, for some reason when creating a new docker container, I don't ever see custom br0.200 (the vlan I created on br0). BUT I can select it when creating a new VM. When I go to the docker settings screen I see the br.200 options for setting up dhcp, but there's no entry in the "gateway" field (even though I have one set on the vlan interface). Here is the info in the "routes" portion: Protocol Route Gateway Metric IPv4 default 192.168.1.1 via br0 1 IPv4 192.168.1.0/24 br0 1 IPv4192.168.1.0/24 br0.200 1 IPv4192.168.1.0/24 bond1 1 IPv6 ::1 lo 256 Anyways, any help is much appreciated. Thanks! tower-diagnostics-20190503-1437.zip
  8. Hey all! Is there an updated link for the client configuration guide? I'm trying to get this setup so that all traffic from only 1 interface (I have two setup NOT bonded) will pass be routed through the vpn tunnel. I'm now stuck on the first step of getting the plugin to connect. I tried to go to the link on the first post for client config guide, but it doesn't take me anywhere. Is there a new one? Thanks!