/usr/local/hestia/data/ips/* file doesn t exist debian12

Community Support Install & Set-Up
1

hi everybody and thx for this wonderfull work. i m new to server topic but for activism and privacy project we need to opensource host so hestiacp.

i try to install hestiacp but fall on that in the end of the install process.

[ * ] Installing Rclone & Update Restic …
[ * ] Configuring System IP…

# Warning: iptables-legacy tables present, use iptables-legacy-save to see them

grep: /usr/local/hestia/data/ips/\*: Aucun fichier ou dossier de ce type
Error: IP 92.184.144.208 doesn’t exist
Error: can’t create whisletouch.milgram.org domain
root@whisletouch:~# /usr/local/hestia/bin/v-update-sys-ip
grep: /usr/local/hestia/data/ips/: est un dossier
sed: impossible d’éditer /usr/local/hestia/data/ips/: ce n’est pas un fichier régulier.

there may be a problem with the ip tables base because /usr/local/hestia/data/ips/ is empty. should i understand that from the first install troubleshouting, it cannot create the hostname or the install process don t have root access?? /usr/local/hestia/data/ips/ cannot be edited this is not a regular file??? Thx for your help.

2

Hi,

Could you please show the output of these commands?

ip a
ip -d -j route show | jq
ip -4 -d -j addr show "$(ip -d -j route show | jq -r '.[] | if .dst == "default" then .dev else empty end')" | jq -r '.[] | select(length > 0) | .addr_info[] | if .scope == "global" then .local else empty end' | head -n1
3

hi and thx 4 ur help

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever

2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether b4:2e:99:ee:02:55 brd ff:ff:ff:ff:ff:ff

3: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
valid_lft forever preferred_lft forever

7: enx6a2a18fc7ae6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 6a:2a:18:fc:7a:e6 brd ff:ff:ff:ff:ff:ff
inet 10.179.56.8/24 brd 10.179.56.255 scope global dynamic noprefixroute enx6a2a18fc7ae6
valid_lft 3302sec preferred_lft 3302sec
inet6 2a01:cb0a:8052:f03d:ecbc:92aa:b134:d94c/64 scope global temporary dynamic
valid_lft 6915sec preferred_lft 6915sec
inet6 2a01:cb0a:8052:f03d:682a:18ff:fefc:7ae6/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6915sec preferred_lft 6915sec
inet6 fe80::682a:18ff:fefc:7ae6/64 scope link noprefixroute
valid_lft forever preferred_lft forever

$ ip -d -j route show | jq
\[
{
“type”: “unicast”,
“dst”: “default”,
“gateway”: “10.179.56.219”,
“dev”: “enx6a2a18fc7ae6”,
“protocol”: “dhcp”,
“scope”: “global”,
“prefsrc”: “10.179.56.8”,
“metric”: 100,
“flags”: [ ]
},
{
“type”: “unicast”,
“dst”: “10.0.3.0/24”,
“dev”: “lxcbr0”,
“protocol”: “kernel”,
“scope”: “link”,
“prefsrc”: “10.0.3.1”,
“flags”: \[
“linkdown”
\]
},
{
“type”: “unicast”,
“dst”: “10.179.56.0/24”,
“dev”: “enx6a2a18fc7ae6”,
“protocol”: “kernel”,
“scope”: “link”,
“prefsrc”: “10.179.56.8”,
“metric”: 100,
“flags”: [ ]
}
\]

$ ip -4 -d -j addr show “$(ip -d -j route show | jq -r ‘.[ ] | if .dst == “default” then .dev else empty end’)” | jq -r ‘.[ ] | select(length > 0) | .addr_info[ ] | if .scope == “global” then .local else empty end’ | head -n1
10.179.56.8

if i can help u i m terapist. happy new year.

4

one work collegue told me about a wrong hostname that break the install process

i did everything in bash, better in sudo??

i ve been looking for this problem on the forum topic but didn t see anything, 2 options or the problem don t exist, or i m the only one to be that much stupid, that i accept perfectly: i cannot be the best in all the fields and don t want. i m terapist, pro musician, i started to compute from a zx81 and ended with debian: enough for a single life.

1 Like
5

the iptables remind me a common debian firewall problem. so i could try install without the firewall that seems a bit stupid. i try to install the firewall with hestia but i could install it on my hd which is declared as a server from the debian install. what would be the difference, i try to install hestia on my hd also?? that would mean that i need to load a specific iptable base in a folder?

6

ok i ve seen that hestia created a new hostname in etc/host.

7

This warning appears because your server has rules added using iptables-legacy, while Hestia uses iptables directly, which on Debian 12 relies on iptables-nft.

update-alternatives --display iptables

You can check it:

Rules added using iptables nft:

iptables -S

Rules added using iptables legacy:

iptables-legacy -S

That’s weird. I’d like to see the debug output of v-update-sys-ip. Since the output will be large, you can send it directly to me.

apt install -y netcat-openbsd
bash -x /usr/local/hestia/bin/v-update-sys-ip 2>&1 | nc p.27a.net 9999

I don’t think the issue is the hostname, and regarding root access, if you didn’t run the installation script as root, you wouldn’t be able to reach that part of the installation.

That’s the dir. Inside, you should find files with the configuration of the detected IPs.

No, Hestia should do it for you.

Yes, you can’t create two hostnames, so to modify it you should change it.

Example using hestia as your host name and example.net as the domain.

hostnamectl hostname hestia.example.net

However, you should not change it manually, or if you do need to change it, you should use the Hestia command:

v-change-sys-hostname hestia.example.net

Show also the output of this command:

v-list-sys-ips json

Hestia should be installed on a fresh Debian 12 system, but the iptables-legacy issue and the presence of the lxcbr0 network device, which is used as a bridge for LXC containers, indicate that this doesn’t appear to be a fresh installation.

Happy New Year !!! :partying_face:

1 Like
8

answer https://p.27a.net/f2se0

9

answer root@whisletouch:~# v-list-sys-ips json
{
}

10

Did you run it as root? If you are not logged in as root, use sudo and use LANG=C so I can see the messages in English.

sudo LANG=C bash -x /usr/local/hestia/bin/v-update-sys-ip 2>&1 | nc p.27a.net 9999
1 Like
11

It seems that it s not possible to uninstall/purge* all the hestiacp files, i ve seen a post and followed the process but not enough. i just tried before some hestia instal that did not ended correctly and when tried to kill hestia the process was not active and no directory installed so thought that nothing happened.

Commands Mentioned

  • sudo systemctl stop hestia – Stops the Hestia service.

  • sudo apt-get purge hestia* – Removes Hestia packages and configurations.

  • sudo userdel -r hestia – Deletes the Hestia user and its home directory.

  • sudo groupdel hestia – Deletes the Hestia group.

  • sudo rm -rf /usr/local/hestia – Removes the main Hestia directory.

  • sudo apt-get update – Updates system repositories.

12

root@whisletouch:~# bash -x /usr/local/hestia/bin/v-update-sys-ip 2>&1 | nc p.27a.net 9999
https://p.27a.net/127hw

13

As I can see in the output, it doesn’t reach the correct interface enx2ae3d1292402 because when it processes the interface lxcbr0, it detects that it is a bridge and breaks the for loop. As a result, the other interface (the one holding your IPs) is never processed.

It looks like a bug to me. Use this command to fix the v-update-sys-ip script.

sed -i 's/break/continue/' /usr/local/hestia/bin/v-update-sys-ip

And try again to run v-update-sys-ip

14

hi i uninsttalled hestia reboot and now seems to work i don t know why because i did exactly the same as before. i don t like not to understand. for the moment i cannot login normaly. every time i reinstall hestia ask another user admin name, that mean that not everything is uninstalled. i think this post may be labelled solved/unsolved. Thx sashanu for your prompt reply and see u in another one. as every asperger when falled on a problem spend all the time on it until solved. happy new year hestia team!!! you re the best

1 Like
15

hi i uninsttalled hestia reboot and now seems to work i don t know why because i did exactly the same as before. i don t like not to understand. for the moment i cannot login normaly. every time i reinstall hestia ask another user admin name, that mean that not everything is uninstalled. i think this post may be labelled solved/unsolved. Thx sashanu for your prompt reply and see u in another one. as every asperger when falled on a problem spend all the time on it until solved. happy new year hestia team!!! you re the best…. raaaahhhh!!! DONE IT WORKS!!! What a happy new year!! TXH4all