Vesta Control Panel - Forum

Any solutions for this?

I am running centos 7, it's now December 2018.

Exact same issue.
iptables shows 0 time, when all other services are fine.


Same issue here. Did you solve it?

Check file /usr/local/vesta/data/firewall/rules.conf and check if the first line of the file is empty. In that ...

It would be great a full list of each change or improvement.

Vesta 0.9.8-24 package is available, but I can't find its release note.

What does this new package release include?

Use this service to check what is wrong with your settings (if something is wrong)

https://www.mail-tester.com/?lang=en

I answer my question: v-add-firewall-chain overwritte the file on boot,

# Preserving chain
chains=$VESTA/data/firewall/chains.conf
check_chain=$(grep "CHAIN='$chain'" $chains 2>/dev/null)
if [ -z "$check_chain" ]; then
echo "CHAIN='$chain' PORT='$port' PROTOCOL='$protocol'" >> $chains
fi


but ...

I've detected that file /usr/local/vesta/data/firewall/chains.conf is restored to its default content each time that the system is rebooted.

Is that usual? Why is it overwritten?

I've detected it on a centos 7 64 fresh install with default vesta installation.

I'm trying limit the users with ssh access on my servers. I've checked that by default admin can access by ssh. Does Vesta require admin user ssh access or can I disable admin ssh access?

Thanks!

geek wrote: Mon Jul 23, 2018 8:47 am Can you provide the issue # or a link to the bug so I or anyone else here can track it?

Here!
https://github.com/serghey-rodin/vesta/issues/1639

imperio wrote: Thu Jul 05, 2018 2:25 pm already opened in our bug tracker

Ah! Ok.
Thanks, Imperio

imperio wrote: Thu Jul 05, 2018 2:11 pm Fix will be soon.
Try to restart iptables

Code: Select all

service iptables restart

well.. the point is that if it's an online server that you can only access over ssh... there is no option to restart iptables after that reboot :)

Anyway, I added it as issue on github too yesterday.