@KosmosCat 

You shouldn't believe everything you read, there are many who don't know what they're talking about, so what you say is not true, you can use port 443 and port 80 for whatever you want.

  @MR.S 

Wow, thanks for replying!
I am very keep on learning more about where I am going wrong.
Will divide subsequent post because I have trouble with posting images and alike

  @KosmosCat 

port NAT is quite simple, it of course requires that your router has a public wan ip

here is an example of port 80

  @MR.S 

I have the setup

modem-er605-TL1008p-{oc200, 2x EAP653, nginxServer}

The controller access config is like below.

however my router redirects me to 192.168.0.2 which is my controller.

Forwarding on 8443 -> 443 works fine and i reach my proxyServer that way but I want to be able to go to to mydomain without specifying a special port

  @KosmosCat 

and if you go to 443 you get to the controller 192.168.0.2 ?

  @MR.S 

Not so easy to see.

From what I understand the OC200 does not support ssh so I cannot open a shell on the receiving end.

If i change the access config to be 443 I get redirected to the controller login page.

I did get to the shell on the er605 but this does not make me much wiser except that redirect_https out to be on.
 

#show ip http configuration 

http_port:                 80

redirect_https:            off

https_port:                443

enable_https:              on

web_timeout:               6

 

#show nat virtual-server

---------------------------------------------------------------------------------------------------

ID     Name      Interface       Exteranl Port   Internal Port   Internal Server Ip     Protocol

---------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------

2      xxxxxx WAN1            8443            443             192.168.0.9            ALL     

---------------------------------------------------------------------------------------------------

3      xxxx WAN1            443             443             192.169.0.9            ALL     

---------------------------------------------------------------------------------------------------

❯ sudo tcpdump -i eth0 port 443 -nn
This yields nothing when i curl mydomain with http (sorry that this forum does not allow me to format as a link)

even if the host was correctly resolved.

Everything works as expected if i visit my domain via port 8443.

But like I stated above, that doesnt really cut it.

Again, thanks for taking your time.

  @MR.S 

OMG! What a silly fool I am!

I have completely overlooked this. Been scratching my head all day and it was staring me straight in the face all the time.

Thank you for taking your time 

  @KosmosCat