You will need console access or a rescue boot disk, neither of which have anything to do with Hestia which means this is the wrong place to expect to receive training in their use.
I apologize for writing here again, but I really need guidance now regarding the Hestia server.
I am incredibly grateful for the valuable time you have taken to provide me with assistance. I have successfully accessed the files on my boot volume by attaching it to another instance.
I’ve added the correct Rules to the file
/usr/local/hestia/data/firewall/rules.conf
I’ve restarted the server but is not working…
Still no connection for dashboard or even ssh on port 22…
The only way i can edit the files is mounting this server to another working instance… that way i can’t use the v-update-firewall…
Should i update the v-update-firewall file with all the new mounted path ?
root@instance-20230607-2318:/mnt/sdb# /mnt/sdb/usr/local/hestia/bin/v-update-firewall
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 19: /etc/profile.d/hestia.sh: No such file or directory
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 21: /etc/hestiacp/hestia.conf: No such file or directory
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 23: /func/main.sh: No such file or directory
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 25: /func/firewall.sh: No such file or directory
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 27: source_conf: command not found
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 33: is_system_enabled: command not found
/mnt/sdb/usr/local/hestia/bin/v-update-firewall: line 40: heal_iptables_links: command not found
I restarted already hoping the v-update-firewall could work…
Sorry, Im just missing this step for v-update-firewall
Yes, i get to the point to execute on chroot environmet the v-update-firewall
i get this error
root@instance-20230607-2318:/home# /usr/local/hestia/bin/v-update-firewall
cat: /proc/cpuinfo: No such file or directory
cat: /proc/cpuinfo: No such file or directory
grep: /proc/1/environ: No such file or directory
Error: Invalid object format: RULE=‘10’ ACTION=‘ACCEPT’ PROTOCOL=‘TCP’ PORT=‘22’ IP=‘0.0.0.0/0’ COMMENT=‘SSH’ SUSPENDED=‘no’ TIME=‘17:14:41’ DATE=‘2014-09-16’
I think im almost there…
should i must leave a blank line at the end of the rules.conf?