System.Net.Sockets.SocketException (13): Permission denied with selinux enabled when starting Kavita about kavita HOT 1 CLOSED

Found the solution, it was a hidden selinux rule:

Jul 24 13:49:53 setroubleshoot[71999]: SELinux is preventing /data/Kavita/Kavita from name_bind access on the tcp_socket port 5000. For complete SELinux messages run: sealert -l 12fee786-2741-47f5-91ca-90d301101db1 Jul 24 13:49:54 setroubleshoot[71999]: SELinux is preventing /data/Kavita/Kavita from name_bind access on the tcp_socket port 5000. ***** Plugin catchall_boolean (89.3 confidence) suggests ****************** If you want to allow httpd to access openstack ports Then you must tell SELinux about this by enabling the 'httpd_use_openstack' boolean. You can read 'httpd_selinux' man page for more details. setsebool -P httpd_use_openstack 1 ***** Plugin catchall (11.6 confidence) suggests ************************** If you believe that Kavita should be allowed name_bind access on the port 5000 tcp_socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. allow this access for now by executing: ausearch -c 'Kavita' --raw | audit2allow -M my-Kavita semodule -X 300 -i my-Kavita.pp#

needed to add
allow httpd_t commplex_main_port_t:tcp_socket name_bind;

as selinux rule

from kavita.