ViciBox v.12.0.2 released

[williamconley]

anyone else having issues with FastAGI not starting with the new install?


/usr/share/astguiclient/FastAGI_log.pl --debugX
SERVER LOGGING ON: LEVEL-4 FILE-/var/log/astguiclient/FastAGIchildLOG.2025-02-06
2025/02/06-09:36:24 VDfastAGI (type Net::Server::PreFork) starting! pid(3241)
Resolved [*]:4577 to [::]:4577, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4577 on host :: with IPv6
2025/02/06-09:36:24 Can't connect to TCP port 4577 on :: [Invalid argument]
at line 66 in file /usr/lib/perl5/vendor_perl/5.26.1/Net/Server/Proto/TCP.pm
2025/02/06-09:36:24 Server closing!

Please do not double-post.

viewtopic.php?f=4&t=42223&p=153914#p153914

[carpenox]

try to disable ipv6

[williamconley]

try to disable ipv6

He did. That's what caused the crash.

[carpenox]

yea he told me in my discord, thats strange though because many people are having this issue

[williamconley]

yea he told me in my discord, thats strange though because many people are having this issue

It's not that strange. A lot of us reflexively disable IPv6 (it offends us as you know, lol). So a lot of people end up with this issue as the OS is not the only thing dealing with IPv6. Many packages do not "verify with the OS" that IPv6 is enabled or disabled and their configuration is then screwy if it's not there. Binding is a particular moment when IPv4 vs IPv6 can crash many applications.

Examples:

Code: Select all

/etc/ssh/sshd_config
ListenAddress 0.0.0.0

/etc/postfix/main.cf.default
inet_protocols = ipv4

/etc/postfix/main.cf
inet_protocols = ipv4


We used to turn off IPv6 in GRUB (totally disable it) but have found that using yast instead causes less issues. Specifically with python-nftables.

[kashinc]

You were absolutely correct; it solved my issue. Thank you!

yea he told me in my discord, thats strange though because many people are having this issue

It's not that strange. A lot of us reflexively disable IPv6 (it offends us as you know, lol). So a lot of people end up with this issue as the OS is not the only thing dealing with IPv6. Many packages do not "verify with the OS" that IPv6 is enabled or disabled and their configuration is then screwy if it's not there. Binding is a particular moment when IPv4 vs IPv6 can crash many applications.

Examples:

Code: Select all

/etc/ssh/sshd_config
ListenAddress 0.0.0.0

/etc/postfix/main.cf.default
inet_protocols = ipv4

/etc/postfix/main.cf
inet_protocols = ipv4


We used to turn off IPv6 in GRUB (totally disable it) but have found that using yast instead causes less issues. Specifically with python-nftables.

[carpenox]

nice, great postback

[carpenox]

anyone else had any issues since the 3916 updates for agent performance reports?

[dspaan]

Hi guys, i've started to tryout the vicibox 12 ISO but i'm running into the problem with yast firewall that was reported on before:



I noticed that if you have a freshly installed system this does not happen, it happens after either running vicibox-express or vicibox-install.

Running zypper ref && zypper up does not fix it.

There is only one instance for ssh in /etc/firewalld/zones/external.xml



So how do i fix this?

By the way i used the ISO from here: http://www.vicibox.com/server/index.html

PS: This still has the specs for Vicibox 11 on that page!

[williamconley]

have you tried firewall-cmd --state at the cli yourself to see what the results are for YOU when you are root?

might be a permissions issue, among the myriad possibilities.

[carpenox]

try this: https://dialer.one/index.php/how-to-fix ... 12-errors/