
-
ijuarez started following [Support] binhex - Prowlarr , Unraid OS version 7.1.4 available , Networking for a container and 3 others
-
Unraid OS version 7.1.4 available
What! my trusty usb stick of 10 years of 4GB is not longer capable, this needs to be fixes. but for real, never have gotten this message, there is only 675MB free what can I delete safely to make space?
-
Networking for a container
So it seems I made this issue a bigger, i found my solution staring at me. Need to enable that and boom it worked.
-
Networking for a container
Thank you for the links and the time to explain, I am still digesting the info. Just to clear a few things up. pfsense is my choice of poison and a cisco 3850 is the managed switch. vlans are managed on pfsense and work as intended. Unraid was not setup with vlans at all, after watching the two youtubes i see where the br whatever can be confusing in my post. My br do not have the i.e. br0.10 on my unraid 3 of the 4 ports are connected to a port on the switch that is on a assigned vlan, hence the 10 20 30. I used macvlan until one the of the updates for unraid stated it was better or more stable to use ipvlan with docker. I also noted that the two examples each user has only one network card and i can see if you have vlans on your network and want your containers or vm;s to have access you have to create the vlans. I may have to revamp my networking. thanks again for taking the time to reply.
-
Networking for a container
I have been putting off asking this question because I wanted to find a solution but have not found one. Background unraid server has a 4 port nic, each port is connected to a different vlan. (10 br0),(20 br1), (30 br5). 10 for servers 20 vpn vlan 30 in house pc's 4th nic not in use Dockers are on either a proxynet, bridge, or brX Recently I've redone my media to follow the Trash guide, my issues was with the script that will stop qbit and move files and restart qbit. I posted about this and got help but i was ignoring the error, no route to host. I ignore it because "there's no way, it's on the same server" qbit is on (br1) or the vlan 20, no issues for the arrs that are on the proxynet, they can talk to it because each arr is also part of (br1) so basically they have an ip from proxynet so they can talk to each other and an ip from (br1) so they can talk to qbit (im sure there's a cleaner way but i like it this way) in the setup there's and api that talks to qbit and script that tells it to pause so mover can do its thing. All of that is working but its not talking to qbit. So when I did the most basic of tests (ping) qbit ip from the terminal ( on the dashboard i click the console button) and pinged qbit and no reply (hence the no route to host error). I thought easy fix add a route from unraids default network ( br0 or vlan 10) to qbit but that doesn't work because there's already routes to each brX network and it should work. Its not a firewall issue. I've added some visuals, the one highlighted is the proxynet for the dockers. I am sure if the was just a vanilla setup that only used bridge or host networking it would not be a problem. any help would be amazing
-
qbittorrent-api trash guides
I appreciate the help but have discovered the issue and completely dismissed it in the logs. "error no route" I have a 4 port nic and each nic has its on vlan subnet, i cannot ping from the shell on the unraid box to the docker container on that other subnet hence the "no route" and why it does not work.
-
qbittorrent-api trash guides
thanks for the reply, I got python installed, i am not a fan of mover either but do like the way trashcan guides set it up with all the arrs. the mover script does not work properly because when the script executes is looking for localhost:8080, but since my qbit is not found at localhost it never connects to the api in order for the mover.py script to run. hence my question, where is the config for the qbittorent-api located so I can modify it to point it to the correct instance.
-
qbittorrent-api trash guides
Re-did my setup following Trash guides the only issue I am having is the Mover using the mover script. It calls to install the qbittorrent-api and its installed fine however my setup is not vanilla and qbit is not in the same subnet as the "localhost". So looking at the config that it is uses on the web, its looking for "localhost:8080". So all this rambing is to ask where on unraid would I find were pip3 install qbittorent-api be installed to so i can modify the config or xml or whatever. thanks in advance
-
Unraiders, What’s Your Server’s Biggest Job at the Moment?
Everything, however for me y hardware is getting old and some of the newer implemented technology I miss out But yeah it has come a long way.
-
[Support] binhex - UrBackup
something changed as it denying permission to that file. You are trying to mount and image to browse thru it or are you restoring it?
-
Starting Web UI for Docker
clear your cache
-
[Support] binhex - UrBackup
did anything change with the share that you are using?
-
[Support] binhex - Prowlarr
oh i stand corrected, you using binhex-vpn apps I do not I have whole vlan for vpn. sorry i will recuse my posts
-
[Support] binhex - Prowlarr
So they are on two separate networks To me you have to add readarr to the binhex-network other wise it will not work. I do this using portainer to add multiple networks to one docker.
-
[Support] binhex - Prowlarr
-
[Support] binhex - Prowlarr
is prowlarr and readarr on the same docker network?