We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
v-rebuild-web-domains with nat ip issue Topic is solved
v-rebuild-web-domains with nat ip issue
Hello,
I recently used the v-rebuild-web-domains bin and I saw that configs file was not generated correctly. All ip address were "ips" instead of "192.168.1.13" in my case.
I checked sources and I edited this :
PS : I am using last Debian stable version.
I recently used the v-rebuild-web-domains bin and I saw that configs file was not generated correctly. All ip address were "ips" instead of "192.168.1.13" in my case.
I checked sources and I edited this :
# Get real ip address
get_real_ip() {
if [ -e "$VESTA/data/ips/$1" ]; then
echo $1
else
nated_ip=$(grep -H "^NAT='$1'" $VESTA/data/ips/*)
echo "$nated_ip" | cut -f 1 -d : | cut -f 7 -d /
fi
}
Now it's working fine.# Get real ip address
get_real_ip() {
if [ -e "$VESTA/data/ips/$1" ]; then
echo $1
else
nated_ip=$(grep -H "^NAT='$1'" $VESTA/data/ips/*)
echo "$nated_ip" | cut -f 2 -d "'"
fi
}
PS : I am using last Debian stable version.
Re: v-rebuild-web-domains with nat ip issue
Ok, The bug was me... !
First, I edited script to get the NAT IP (useless and stupide... we want the local ip...).
After that, the issue raised because I have set my env with VESTA=/usr/local/vesta/. But script use cut with "/" as delimiter so...
I have change my env to set VESTA=/usr/local/vesta
Sorry about that :).
First, I edited script to get the NAT IP (useless and stupide... we want the local ip...).
After that, the issue raised because I have set my env with VESTA=/usr/local/vesta/. But script use cut with "/" as delimiter so...
I have change my env to set VESTA=/usr/local/vesta
Sorry about that :).