Unable to access to internal server web from outside through DNAT firewall rule

Could you also provide a screenshot of the DNAT rule itself?

This is the firewall rule, not the DNAT rule itself. It is under the NAT rules tab and likely also had SAGEX3 in its name.

...

This is still a firewall rule, see my screenshot for the NAT rules

Any one can help please

You should not have MASQ enabled for DNAT since I presume you want your internal server to respond to the public IP address on the WAN.  Did you follow this Sophos guide?
Sophos DNAT guide

Thank u for ur reply just simple question regarding the port number in my case I have 8224 of port to reach the server does i put 8224 for both service and pat? 

i followed the guide above but i allways got the same error

and when i try to access the server  throuph public IP it blocked 

no rule matched

i followed the guide above but i allways got the same error

and when i try to access the server  throuph public IP it blocked 

no rule matched

Very simple your external port range should be 1:65535.

Ian

Good day Rachid,

I suggest, if you are still having difficulty, to use the NAT Server Access Assistant found here:
Rules and policies > NAT rules > Add NAT rule > Server access assistant (DNAT)

I just tried this for an internal server.  It asks a couple of questions then automatically creates the DNAT & Reflexive rules along with the required firewall rule.  This only took a minute or two to get working for my particular server.

To follow-up on this, it appears you can only configure internal servers using IPv4 and not IPv6.  Unless I am missing something, the NAT and firewall rules for IPv6 have no #Ports meaning I cannot configure them to receive requests incoming on any #Ports.

Thank You Very Much i will try your solution.

Your Policy Check will not work that way because you try from the same IP as you try to access. 

Try as a source IP in the Policy Check 1.2.3.4 to check, if the internet has access. If still no FW rule is matching, your firewall rule is not right. But try in the policy check: tcp://YOURWANIP:8244 instead. I am not sure, if you do https:// here, if it does not try 443 instead.