Service got SIGTERM if I opened new port on host.

[renegadevi]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug

If I add a port on Linux RHEL-variants using Firewall-cmd to public zone, it got killed.

Nginx Proxy Manager Version

v2.9.18

To Reproduce Steps to reproduce the behavior:

1. SSH into the device
2. Add a port to public zone on host machine: # firewall-cmd --zone=public --add-port=3000/tcp --permanent
3. Nginx Proxy Manager Service crashes. It's no longer running.

Expected behavior

Reload the service it self at most.

Screenshots

Operating System

Rocky Linux 8.5 (RHEL)

Additional context

using podman version: 3.4.2
podman-composer version  1.0.3
firewall-cmd version: 0.9.3

Last logs from container:

[s6-finish] waiting for services.
[9/17/2022] [9:23:09 AM] [Global   ] › ℹ  info      PID 249 received SIGTERM
[9/17/2022] [9:23:09 AM] [Global   ] › ℹ  info      Stopping.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_perms.sh: executing... 
Changing ownership of /data/logs to 0:0
[cont-init.d] 01_perms.sh: exited 0.
[cont-init.d] 01_s6-secret-init.sh: executing... 
[cont-init.d] 01_s6-secret-init.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

Maybe this is completely an issue just with Podman/Linux/Firewalld it self that it decided to kill it by sending a SIGTERM.

The solution was just to reboot.