System problem on Application (Settings --> Advanced Settings)
Description
Problem/Justification
Impact
Activity
Arkan M Gerges Anabi November 23, 2021 at 11:15 AM
Hi Waqar,
Ok, I put the settings like the following, and I could reach TrueNAS Scale through the dns,
Thank you,
Arkan
Waqar Ahmed November 23, 2021 at 11:01 AM
i am not sure why would/should that work ? K8s traffic will be routed to your scale node ip and then do you have another routing rule for routing it from there to some other place ? I am still confused why you need to do that at all if at the end you want to use 192.168.1.1 as the gateway
Arkan M Gerges Anabi November 23, 2021 at 10:42 AM
Hi Waqar,
This node ip (192.168.1.50) is connected to the router as it's own gateway (192.168.1.1), and I thought that the apps from k8s, if they are using the node ip, it can use it also as a gateway. In this situation the node will route the traffic to the outside because it has the default gateway is set on 192.168.1.1
Waqar Ahmed November 23, 2021 at 10:31 AM
is your SCALE node ip the default gateway ? I am not sure i follow the motivation behind setting it as the gateway ?
Arkan M Gerges Anabi November 23, 2021 at 9:06 AM
Hi Waqar,
192.168.1.50 is my TrueNAS Scale node IP.
After I changed it again as in the second screenshot (with node ip: 192.168.1.50),
I can reach through my local ip (home router)
I can not reach through dns
Also I attached the following scrrenshot from Alerts (when I've changed the settings as in the second screenshot with node ip: 192.168.1.50)
I attached the save debug in private section (after I returned the settings to original as in the first screenshot with node ip: 0.0.0.0) and now I can again reach TrueNAS through my dns again,
Thanks,
Arkan
Before I change something in the "Settings" dropdown (on the left of Launch Docker Image button), I saved my truenas config, then I've changed the settings as follows: node ip from 0.0.0.0 to my node ip ehternet interface to the physical interface then save.
After that nothing is working:
I can not access to the webui
I can not ssh to my user
Then I successfully restored it by putting the monitor cable into my physical server and hard reboot it, then from the shell I've entered the config settings of kubernetes, and it gave me back the local ip to login, then I've restored the settings.
This is the origianl settings:
This is the one that broke it:
Thanks,
Arkan