-
|
I'm not sure if this is a known thing, something I'm doing wrong, or what. I am in the process of moving my apps over to jailmaker. I used the docker template to build my jail and following the linked YouTube video I setup Dockge. So far, so good. Now, I have avoided using Truecharts for apps for most things, but I do have 2 apps that TrueNAS native charts didn't have (Flaresolverr and Unpackerr). I figured Flaresolverr would be a good "test" of my jail (no environment variables or data sets to mount, a very basic app) so I deployed that using Dockge and its working. If I go to http://192.168.20.100:8191 (my jail's IP) I get a response from Flaresolverr and I see in the logs that it logged the connection. However, I then tried to point my Prowlarr instance (running the TrueNAS native Prowlarr) at the new IP and it fails to connect. No connection is logged. I've run the following tests:
At this point, I am lost. All my network checks check out, but for some reason Prowlarr cannot reach this one IP. My guess is something about the TrueNAS apps network, but why just the jail IP? Anyway, is this something anyone else has run into and is there a way to make this work? I was trying to avoid a full lift and shift to jailmaker, preferring to migrate one app at a time, but I guess if I have to tear it all down that's what I'll do. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
|
I would recommend you share more details about your setup (per #135 - How to ask for help? specifically the Troubleshooting and Collecting infromation section) We cannot make assumptions of your setup from your description. Are you using a bridge or macvlan? How is your K3s cluster configured? Are there any static routes setup on your TrueNAS networking setup? Are there any specific interfaces assigned. There are probably other questions as well, gather as much information as you can, and maybe we can figure out together where to look next for the solution |
Beta Was this translation helpful? Give feedback.
-
|
as for 3. - is the NAS IP range and your LAN IP range different? Also, what's the network setup within the jail? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I totally understand as well. I work in IT so I totally get the "user didn't provide enough info" thing, but, well, sometimes its also good to know what you don't know and just wait until someone asks you for things then posting irrelevant info like crazy. I understand I am taking this from a "network engineer" perspective, which may not be a valid approach. If you are unclear about what I am doing and/or am trying to accomplish then by all means ask and I will do my best to clarify. I appreciate the effort. cli -c 'app kubernetes config' cli -c 'network general summary' cli -c 'network configuration config' All I removed was my domain name since since it is public so I can issue certificates for things. My NAS's main interface is on what I call my "server network" where I have my NAS, and a Proxmox host with a few VMs/LXCs running. So I bound Samba to a separate interface and connected that to my LAN to avoid traversing the firewall when running my backups or accessing SMB shares. I think I was seeing some random traffic going out the wrong interface and so I added the static default route and that had stabilized things. I don't entirely remember as I did that probably a year ago or more. You are correct that I shouldn't need it since the system default gateway is the server network gateway any way. I removed it for now and I am not seeing any issues so I will leave it for now if it simplifies things while we troubleshoot. However, it didn't change the issue status. The only change I did inside the jail is the recommended network changes from the networking part of the Read Me. Here is what's inside my 80-container-host0.network file (I commented out the original network section instead of overwriting it entirely, but that should not make a difference): As for Docker, I'm a noob so bare with me. I haven't done any customization to the networking beyond the base install using the template provided. This was my first app to attempt to deploy on my own without a tutorial to back me up. That being said, does this help? Its the output of docker network inspect flaresolverr_default I should note again that my flaresolverr container is accessible from literally every other device/VM that I have tried from on my network, so I don't believe this is a "network" issue, at least not in an external routing/firewall sense. It is only when trying to access from a TrueNAS app that I have the issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'm the same with you, ex Network IT guy with software developmeent and database development background - can't call myself engineer, because everything was self-taught or OJT, so there are gaps - but have enough experience under my belt. So don't feel bad, you're in good company (I hope 🤭) Anyway, when I think of processes, flows etc, I think visually, and so I drew what I understood from your setup and findings. How is the Prowlarr app's networking defined in TrueNAS ? I can tell you that I run a DNS server inside a jail, and my TrueNAS Chart apps reach the DNS server, but I'm not running any TrueNAS SCALE native apps. flowchart
direction TB
subgraph gw["Gateway"]
subgraph gw_c["Settings
ip: 192.168.20.1
"]
end
end
url(["Click here to open diagram in live editor"])
subgraph c["Computer on LAN"]
subgraph c_c["Settings
subnet: 192.168.20.0/24 ?
"]
end
c_curl_jdf_p(["curl http://192.168.20.100:8191/"])
end
subgraph t["TrueNAS SCALE"]
direction TB
subgraph t_s["shell"]
t_curl_jdf_p(["curl http://192.168.20.100:8191/"])
end
subgraph t_c["Settings
hostname: NJ-NAS-01
domain: <removed>
ipv4gateway: 192.168.20.1
nameserver1: 192.168.20.1
hostname_local: NJ-NAS-01
"]
end
subgraph k["TrueNAS Apps (k3s)"]
direction TB
subgraph k_c["settings:
id: 1
pool: Application
cluster_cidr: 172.16.0.0/16
service_cidr: 172.17.0.0/16
cluster_dns_ip: 172.17.0.10
route_v4_interface: br0
route_v4_gateway: 192.168.20.1
route_v6_interface: null
route_v6_gateway: null
node_ip: 192.168.20.50
configure_gpus: true
servicelb: true
passthrough_mode: false
metrics_server: false
dataset: Application/ix-applications
"]
end
subgraph kp["Prowlarr"]
direction TB
subgraph kp_c["Settings:
Type: TrueNAS SCALE 'native' (not TrueCharts)
"]
end
subgraph kp_s["shell"]
kp_p_gw(["ping gateway"])
kp_p_t(["ping TrueNAS"])
kp_p_j(["ping jail"])
end
end
end
subgraph j["jail (docker)"]
direction TB
subgraph j_c["Settings:
Jail name: docker
Static IP: 192.168.20.100/24
Gateway: 192.168.20.1
"]
end
subgraph j_s["shell"]
j_p_gw(["ping gateway"])
j_p_t(["ping TrueNAS"])
j_curl_jdf_p(["curl http://192.168.20.100:8191/"])
end
subgraph jd["docker"]
direction TB
subgraph jdf["container: Flaresolverr"]
direction TB
subgraph jdf_c["Settings:
networking: bridge mode (default)
"]
end
jdf_p((("port 8191")))
end
end
subgraph j_n["Network interfaces"]
br0_j((("br0")))
end
end
subgraph t_n["Network interfaces"]
eno0((("eno0")))
br0((("br0")))
eno0 -.->|Assign| br0
end
end
br0 -...->|Assign | br0_j
kp_p_t --->|Success| br0
j_p_t --->|Success| br0
kp_p_gw ---->|Success| gw
j_p_gw ----------->|Success| gw
kp_p_j ---------->|Fail | j
c_curl_jdf_p ----------->|Success| jdf_p
t_curl_jdf_p -------->|Success| jdf_p
j_curl_jdf_p ------>|Success| jdf_p
url o--o c
click url "https://mermaid.live/edit#pako:eNqlV1tv2zYU_iuEBrQ2ENlWlqWtCnTwsrVYUQQFnLeqEBiJ1sUyKZCUvaDpf9-haN0oKk5bPknUp3POd67kNydiMXF8Z1uwY5RiLgOKYMUZJ5HMGEV3f-kdUd0nHJcpSo5fAucDluSIHwLnq_5qIMIIMBsiZUYT0SHUykofeW8uF97168XlauF1XwfCCI31S_2gHytezEDuTZFFO5QSTpBkiJWEgrkYVO9RRlGRHQgicSYZB4Fzw3hl1w3bl5UkHAG7T-tbO4foCQoAokQOaKyWl1foz3Nc1ALBwCPM421YKjbqDaVSlv5y2ffLauW_9t54y45EzxOtmRIk3PGK3K43aHOz_vTPQPEwihaWMhQgQKSkKAY_qiV_2tAR556-aa-mTEiK98RvNm4_ukDLXXlDXMz2OKN-t_GikG852bMDiV8k8q2ZboerRCer_sWee2op5YLwA-HeOWhja1iwCBe-1dbpFGjdsetFb12WAs12v4v5KBLjYhxLqh0rTo71DR_EPjKXQahkrDBBYBFUGlaKh-CoqATUTxhlMW9-8l4pXy1UJXjXhpHg0ywiY_grK7yRHlMRqmYxgHurIZgzqOTwcBVmFP7Z4gjS555PgXqJMB3bE_q6L5JWUCB2VE_mGEWhubYkGuqd5j8MQyNGt1lScRImZSX0XxLyw-rP4r4ndowqsRAyBTOTNNyDGQq8xYUwYHsieRaJUCe-lmiBxVhioXqePT-W2X8u7l6Nyh4ldL052BnUxzCzS0jsz5wdC8y5VdJ0eRiCBs3HH0PvHkpw06CdopcUGB3ISzSjTNbfbtSUFHMLI5txI2KmTdMNuFkAKsPkqHpwCZajpJ298yd-kC3-ROgMPm_xOc4KO3hEZrBh73E5iFUS0Sxm0Y7wn2pv-bnQfVQa9PTQasaQjYRIRujfz8Pzx0qN7jH6Q1PW041iRGQ6ifMzYc5_IML584Ob_9IIP0MpBoEnX_9CVYJtyjBGJQx11YDeQ50TwQroRnyyJJ4Wbio4lzxttybyyPgOUGqIZHFCkOqckLlki6tCTpTPpJXW2q_jUgdkNoMYMi6R8n3gzOc_XHFGjlGgeas5oHZ4Cat5MCOh4pUFalqOdT-jsOVz9RHKVrUq9WDRBRY8aQlbIXfhvntcC5El9HE43233BACYfN3FohOBHjV_jdbd0sS7gN5UEfARPY25BTqFPbVtE9rHJsdObIt0u2WB6l6NRth3j-9VC0TA7cSrf9GYEFp_0-j-ab8v2Y7ODXSDH6PbmxtirstQdLKtvsKp3cBR_UhAQ9oTDgf7eKEucEt1gfutxDvmQ-ACBzW3PsuFr7nrofC-wHTnXDgnSXCr_abUBY5MyZ4Ejg-PMea7wAnod8DhSrLNA40cXx2fLpz6sOT49fHnwqlKOPSQv7UiDfn-P6B2CJw" "Click to open diagram in editor" _blank
|
Beta Was this translation helpful? Give feedback.
-
|
Wow, that looks pretty good to me at first glance. I appreciate the hard work and the help, but I may have actually literally solved my issue as you were posting this. I noticed in the TrueNAS GUI that I had a new interface (I assume this is created by the "jlmkr create" command) called "vb-docker". I bound this to my br0 interface in the TrueNAS GUI, and now everything can talk to each other just fine. Its interesting that that would break comms between K3s and the jail, but not the host and the jail, but it seems to have done the trick. I double-checked the documents and I don't see anything about needing to do this, so I don't know if this is a "bug" or just something finicky about my system. Of course, if anyone sees a reason why doing this would be a bad idea, please let me know. Otherwise, I believe this is the solution. |
Beta Was this translation helpful? Give feedback.
-
|
I'm marking that as the solution, in case anyone else runs into the same thing. Now that I have added the vb-docker interface as a member interface under my br0 interface in the TrueNAS GUI, this is definitely now working as expected and has been stable for 24 hours. Appreciate the help given.
|
Beta Was this translation helpful? Give feedback.
-
|
That IS strange, because cb-docker is supposed to be bound to br0 to begin with. |
Beta Was this translation helpful? Give feedback.
-
|
I've made an account to write a reply for I'm having this exact same issue, but worse. When I try to ping from my jail or from one of the apps, I am unable too reach either of them. I noticed the vb-docker as well after making a bridge (in the hopes that would fix my issues), but alas my luck is not the same. after doing so I still cannot commuincate across the docker images and the truenas apps. I've read through what you've written 3 times over, and my bridge file is set up the same way, just different IP addresses. Would it be possible to get a picture of your bridge setup fully? I see your jails ip's are ending in 100 and the apps in 50 so wondering if it's also my docker image setup of my jail or docge itself. Any help here would be appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Matt-Of-Doom, it look like @SonicJoe answered you below. If that's not the answer, please Please open a new discussion. You can reference this discussion by typing |
Beta Was this translation helpful? Give feedback.
-
|
So your TrueNAS box should be using the bridge interface as its IP, and then you join vb-docker to the bridge. However, I was actually going to update this since I had an issue upon reboot. I would not recommend this as a long term solution, as it causes issues bringing the network up on reboot. Its fine for a short duration as you migrate things, and as long as you have access to the console in case your system reboots. Anyway, my networking looks like this:
enp4s0 is a standalone interface going to my "LAN" network The bridge settings would look like this after you add vb-docker:
Just, remove vb-docker from br0 before rebooting for any reason, as the bridge interface won't come up if its there on boot. Or at least, it wouldn't for me. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, Thank you for the pictures! I had mine set up in a similiar way, but seems like there might be some key differences. good to know about removing vb-docker if going for a reboot. To clairfy you have enp4s0 which is your LAN is where you TrueNas box sits Both enp4s0 and enp5s0 are physical interfaces on that device br0 connects enp5s0 and the vb-docker together I also see your bridge IP address range and your enp4s0 IP address range are different. so the question is Did you intnetionally seperate them into 2 different IP address and if so how are you getting them to talk to one another? If this is out of the scope of TrueNas that is fine but seems like your jails are in 1 network and the truenas box is on another. Is this something that can be set up in scale? |
Beta Was this translation helpful? Give feedback.
-
No, my TrueNAS main interface sits on a network I call my "server network", which is the one enp5s0 is connected to.
Correct
Yes, and enp5s0 connects everything physically to the rest of the network
Yes, I believe I mentioned it earlier when working with Lockszmith-GH. enp4s0 is on my LAN which is the network where all my personal devices live. Windows PCs, mobile phones, tablets, etc. The bridge interface is on my "server network" where all my services live. Really just a virtual wireless controller and a few other VMs I have for playing/learning with, nothing fancy. I set it up that way so when my LAN devices are accessing my SMB share the firewall doesn't have to process all of that traffic. The firewall handles routing between the two networks for other services.
My jail is on the same network as my TrueNAS box. If you had more than one network, I believe there is a way to make the jail bound to more than one network. I know I saw something in the jailmaker documentation, but its not my use case so I can't help there. For binding to a single network, you just set that first line in the arguments per the template: systemd_nspawn_user_args=--network-bridge=br0 That tells systemd-nspawn to bind the container to the bridge interface with label br0. There are other options you can use, if you look through the documentation. |
Beta Was this translation helpful? Give feedback.
Wow, that looks pretty good to me at first glance. I appreciate the hard work and the help, but I may have actually literally solved my issue as you were posting this.
I noticed in the TrueNAS GUI that I had a new interface (I assume this is created by the "jlmkr create" command) called "vb-docker". I bound this to my br0 interface in the TrueNAS GUI, and now everything can talk to each other just fine. Its interesting that that would break comms between K3s and the jail, but not the host and the jail, but it seems to have done the trick. I double-checked the documents and I don't see anything about needing to do this, so I don't know if this is a "bug" or just something finicky about my …