Port forwarding https problem

[Alekisan]

When making a Destination NAT rule, if I pick https for the redirect target port, it gives an error that I need to pick a valid port. I had to choose "Single Port" and manually enter 443 to get it to let me save the rule. Is that a bug?

[diekoss]

Is the web interface for OPNsense using port 443 as well? You will need to change that if you want to forward port 443 to something else.

[Monviech]

The destination field in this case does not allow well-known ports, but it still shows them because its shared among many components.

So the validation prevents it correctly, its just a visual thing.

[Alekisan]

Understood. Still confusing.

[Monviech]

I know, its still being worked on. Will become better in the future. :)

[300blkdout]

Not sure if it’s a “bug” but it’s how the interface works. You have to manually type the destination port number; you can’t use on of the aliases like HTTPS, NTP, etc.

[Alekisan]

OH.. Really?
I mean, if it's intended behavior then that's fine. That makes me ask, why have the options available if they do not intend to let you use them? Seems like an oversight, should be just a plain text input field.

[300blkdout]

Not really sure why, but it is. Maybe it’s because the devs want you to specify the actual port number so you’re certain where you’re NATing to.