Closed mighkel closed 5 months ago
This problem is related to ZTI getting an inappropriate IP addr for the use case. The default IP address is obtained via http://ifconfig.me/ip.
We could use alternate ansible roles or environment variables to distinguish between the use cases:
I wouldn't suggest to compromise the nature of "ZeroTouch" by making it "Well, maybe a couple of touches..." but the Custom Deployment (Advanced) Ansible install, while asking for user input for package selection, could prompt the user to input the desired IP, be it the public IP, or their VPN IP.
Taking it a step further:
"Do you have VPN installed?" Y
"Enter the public (non-VPN) IPv4 address:" 123.456.0.91
"Enter the VPN IPv4 address:" 123.987.0.42
"Route all FTS traffic through VPN [123.987.0.42] ?" Y
If Y, then config firewall to allow all FTS ports in/out VPN IP, and only allow SSH in on public IP. User can close that later.
@mighkel I made a fix that should accommodate most of the use cases.
The easy_install.sh
takes an additional argument --ip-addr
which can be used to suppress guessing of the IP address and provide the address to be used.
The user documentation has a corresponding PR which describes the revised approach for installing which should be committed soon.
wget -qO - bit.ly/freetakhub2 | sudo bash -s -- --ip-addr 123.456.0.91
Installed FTS-UI via Zero-Touch on Ubuntu 22.04 on SSDNodes VPS
wget -qO - bit.ly/freetakhub2 | sudo bash
Per:https://freetakteam.github.io/FreeTAKServer-User-Docs/Installation/Ansible/ZeroTouchInstall/
After install, entered [IPv4 address]:5000, and UI login displays. Attempt to login (admin:password) Result:
Ansible Log: