Challenges of Version 16.0.19

Hello:

Since upgrading to 16.0.19, I have seen a couple of key challenges. I think generally the new release is nicer than the old ones. It just may have a copy of "minor" issues.

1. The firewall will often lock out external users both at the SIP level and will not allow me to use HTTP or HTTPS to access the FreePBX system. If I turn off the firewall (fwconsole firewall disable), then the users are allowed to connect. The remote users are from one ip (and they are nat'ed). Did not have this issue in version 14 of FreePBX. If you do turn off the firewall, after some period of time, it starts again locking out users (and me) so I must then go back into the server via the EXSI console and unlock it again.
2. In changing the admin password, you can enter the password (and you think you are saving it) but after you log out, the new password is not available and I must use the fwconsole unlock function to get back inside. This gets a bit upsetting during stress times.

Overall, the improvements in 16 are useful. However locking out users at the firewall is not good as I am getting tired of the team here in Laurel calling to fix it.

Thank you.

The configuration is: Our servers are located in a rack in a Cogent data center that is 2.5 hours from where I am. There is a router in our rack that have a number of ACL's on it that control who has access to various servers. The FreePBX has a public IP on it but the router limits who can get to that IP. Not as a firewall but more of a gatekeeper. It is the same ACL we have used for years. No changes. The only IP addresses currently allowed that FreePBX instance are from one specific IP address.