For Traffic Rules, I have this. Hmm… Wan to Device. Should it be WAN to LAN and destination address is the Server’s LAN IP? I think I tested that as well and it didn’t work.
From rule counters it seems like no packets with specified match have arrived. So either router is unreachable via public IP or something is wrong with port forward rule
To fully check if it is not the first.
Ping device via public ip
In access control enable remote http(s) and check if WebUI is reachable via public IP.
Change remote WebUI ports to 4444 and 8080 to check if ISP is not blocking non-standard ports. (disable created port forward rule so it would not interfere with this test)
About second:
Did you just created port forward rule or changed something in edit?
Besides one port forward and one traffic rule did you changed/added anything else in firewall pages?
Also about traffic rule: just remove it as port forward already handles allowing traffic from wan zone.
”Did you just created port forward rule or changed something in edit?”
I have tries several ways to setup this. It is possible that I edited the rule which I initially created.
”Besides one port forward and one traffic rule did you changed/added anything else in firewall pages”
Not sure anymore.
If WebUI via public IP works with both default and non-default ports then I recommend resetting device and just creating two simple port forward rules without any other firewall changes.
For starters, the RUTx50 is already in rpoducton having Site-t-Site VPN to 5 diffrenet Remote LANs. Can’t really reset the box. Maybe there is an eventviewer or log to check what goes wrong. Enabling Remote Access to HTTP (80) and HTTPS (443) didn’t help.
Can you please double check that my settings seems to be good.
What if I delete current Port forwarding Rule and recreate it. Will it create new Traffic Rules and that may solve the problem?
At Traffic Rules. Should I allow 4444 from WAN to LAN to the Server’s LAN IP?
Enabling Remote Access was just to test if you can reach your device via specific ports using simpler configuration. It was not intended to help your port forward. For your port forward you don’t need ANY traffic rules nor any should be created automatically (although it should not cause any problems).
Via forum is is very hard to diagnose what is wrong when your device when has a lot of unrelated configurations. Maybe support will help for you.
For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 16320.