@Kevin_Z 

It got fixed automatically but just now it started failing again. Acces to the instance is fine with internal IP adress and the cert shows fine. But accessing with the DNS name shows that it reconnects to internal router. Why is there no option to change the outside interface port? The software is still on 1.2.2 Build 20220317 rel.50456(4555)

Kind regards

Jasper 

  @venhoute 

Hi,

Do you get that "Local Management via HTTPS is disabled" page only when you browse to your "https://...." link from a device that is currently connected to the local network of your AX73 or do you also get that page when you browse to "https://...." from an external network? (for example via smartphone cellular network)

  @woozle Yea the management seems to be disabled to the outside since I can't access anything from the outside. I just get that the adress is not found.

 Still the same error occurs, I there a solution or should I replace my TP-Link to another brand ?

Same problem on Acrcher C7, it forwards port 80 just fine but it does not let forward 443.

Tried to enable and disable local management via HTTPS but to no avail.

  @venhoute I ran into this same problem.  Posting here on what I did to try and help anyone else who might run into this.  I went into System/Administration and enabled remote management. Then I switched the port to something random.  After I did this, I was able to get my port forwarding to route 443 to my host on my network.  My assumption is that by default the router is watching on 443 to show the https disabled message from your post.  Once I told the router to enable management on another port, my port forwarding settings actually kicked in.  Kind of annoying that I have to enable remote management and potentially expose myself just to get 443 to go through, but I guess this is what I'll have to live with for now.  I hope this helps the next person that runs into this issue.