Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)
Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)
2018-05-10 01:08:41 - last edited 2021-07-13 07:26:51
Model : TL-MR3420

Hardware Version :

Firmware Version :

ISP :

I am trying to access the management console remotely over the public internet but all requests to get the static files (js, css etc) return 403 (as can be seen in browser console). This makes it impossible to login. What I get is a screen like in the attached image.



  0      
  0      
#1
Options
3 Reply
Re:Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)
2018-05-10 15:51:18 - last edited 2021-07-13 07:26:51
For your issue, it's better send email to support@tp-link.com directly.
Provide the HW & FW version, login username and password, WAN connection type and with configuration files.
Their senior engineer will help you test it.
  0  
  0  
#2
Options
Re:Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)
2021-07-12 21:18:53 - last edited 2021-07-13 07:26:51
Did you ever get to the bottom of this? I have this exact problem with my tp-link router too!
  0  
  0  
#3
Options
Re:Problems accessing remote management over internet for TL-MR3420 (403 errors for static files)
2021-07-12 21:23:53 - last edited 2021-07-13 07:26:51

Oh to reply to myself in case it's useful for anyone else - I was accessing my router using a hostname that directs to my home network's internet-facing static IP address. I changed to entering the static IP address directly and now it works. Strange but at least I have a workaround.

  2  
  2  
#4
Options