- Joined
- Jul 31, 2018
- Messages
- 19
- Reaction score
- 8
Hi Everyone,
Over the weekend, I upgraded from 15.5 to 16 on my Windows server on Amazon AWS. This was a typical upgrade: backup 15.5, uninstall 15.5, install 16, configure from backup.
Happily, everything went smoothly except one thing. The firewall check is failing as it checks the 3CX Media Server ports. The error I get is Mapping does not match x. Mapping is y - where x and y are two different ports. This is an error I did not see on 15.5 on the same box.
This does not happen to the same ports consistently. One check and 6 random ports gave me this error, another check and 1 random port giving the error. Each run yields different results, and different ports.
I followed the link here: https://www.3cx.com/docs/firewall-checker/. It seem to indicate the issue is Port Preservation. but it does not give any suggested remediation steps.
Has anyone encountered this on V16, or on AWS? With this being an AWS environment, there is not much I can do in way of router configuration.
It is important to note: the system has been running fine with no reported issues. So i'm not entirely sure how big of a deal this is.
Over the weekend, I upgraded from 15.5 to 16 on my Windows server on Amazon AWS. This was a typical upgrade: backup 15.5, uninstall 15.5, install 16, configure from backup.
Happily, everything went smoothly except one thing. The firewall check is failing as it checks the 3CX Media Server ports. The error I get is Mapping does not match x. Mapping is y - where x and y are two different ports. This is an error I did not see on 15.5 on the same box.
This does not happen to the same ports consistently. One check and 6 random ports gave me this error, another check and 1 random port giving the error. Each run yields different results, and different ports.
I followed the link here: https://www.3cx.com/docs/firewall-checker/. It seem to indicate the issue is Port Preservation. but it does not give any suggested remediation steps.
Has anyone encountered this on V16, or on AWS? With this being an AWS environment, there is not much I can do in way of router configuration.
It is important to note: the system has been running fine with no reported issues. So i'm not entirely sure how big of a deal this is.