Router not port forwarding port 443
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I'm having a weird problem for a couple of days now and it's regarding port forwarding. I have an DNS record pointing at my Ip address.
This way I can acces it with https:// to route it internally to my rpi HA instance.
This worked fine for like half a year since now, it seems to not forward the request and instead tries to show me the router page itself? This has never happened before.
Now when I use HTTP is goes trough and shows me the tp link router instead of the home assistant page.
Locally everything works fine. This is my port forward:
.
Im really confused as to why it doesnt just port forward it and instead tries to handle the request itselfs.
Guessing its because of a software update.
Kind regards
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @venhoute
Do you mean this issue starts after you upgraded the router firmware to the latest 1.2.2 version? Was there anything else changed? Can I have the detailed network layout?
Please be sure you can access the HA in the local network without an issue, and try with another port if possible just to confirm if the port forwarding still works.
- Copy Link
- Report Inappropriate Content
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
- Copy Link
- Report Inappropriate Content
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)
- Copy Link
- Report Inappropriate Content
@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.
- Copy Link
- Report Inappropriate Content
Still the same error occurs, I there a solution or should I replace my TP-Link to another brand ?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
@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.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 4447
Replies: 8
Voters 0
No one has voted for it yet.