[SOLVED] Error 403 FORBIDDEN when accessing the WEBUI thru Reverse-Proxy

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

[SOLVED] Error 403 FORBIDDEN when accessing the WEBUI thru Reverse-Proxy

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
[SOLVED] Error 403 FORBIDDEN when accessing the WEBUI thru Reverse-Proxy
[SOLVED] Error 403 FORBIDDEN when accessing the WEBUI thru Reverse-Proxy
2023-07-28 15:31:49 - last edited 2023-07-31 03:06:49
Model: Archer MR600  
Hardware Version: V3
Firmware Version: ‪1.1.0 0.9.1 v0001.0 Build 220727 Rel.74013n

my MR 600 LAN interface IP address is configured with 192.168.0.1/24, and I also defined a dns entry in my local openmasq server, so that 192.168.0.1 <-> router.home

 

  • I can access the MR600  WEB UI  thru http://192.168.0.1   from a local PC without any issue    
  •  but with http://router.home, it gives an error 403 forbidden 
  • both ping and nslookup on router.home work fine.

 

  • also, I defined a vhost entry in my Apache proxy, to acces it remotely after nat/pat in the MR600 itself,  such as : 

 

<VirtualHost *:443>
        ServerName <MR600WEBUI>
       RewriteCond "%{HTTP_HOST}" "^<MR600WEBUI>$" [NC]
      RewriteRule "^/(.*)"      "http://192.168.0.1/$1"  [P] [R=permanent,L]
</VirtualHost>

 

same problem, error 403

 

 

 

 

 

 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Error 403 when accessing the WEBUI thru router FQDN or remotely thru Reverse-Proxy-Solution
2023-07-30 16:19:29 - last edited 2023-07-31 03:06:49

  @t0urista 

 

I found  the solution, I added one line in the Apache  vhost config, to change the referrer header, and it works pretty well remotely  :

 

<VirtualHost *:443>
     ServerName <MR600WEBUI>
    RewriteCond "%{HTTP_HOST}" "^<MR600WEBUI>$" [NC]
    RewriteRule "^/(.*)"      "http://192.168.0.1/$1"  [P] [R=permanent,L]
    RequestHeader set Referer "http://192.168.0.1"
</VirtualHost>

 

I can access the web ui remotely :

  • nat/pat in the MR600 itself,
  • transfer to the reverse-proxy running on Apache
  • back to the WEB UI IP on the MR600
Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:Error 403 when accessing the WEBUI thru router FQDN or remotely thru Reverse-Proxy-Solution
2023-07-30 16:19:29 - last edited 2023-07-31 03:06:49

  @t0urista 

 

I found  the solution, I added one line in the Apache  vhost config, to change the referrer header, and it works pretty well remotely  :

 

<VirtualHost *:443>
     ServerName <MR600WEBUI>
    RewriteCond "%{HTTP_HOST}" "^<MR600WEBUI>$" [NC]
    RewriteRule "^/(.*)"      "http://192.168.0.1/$1"  [P] [R=permanent,L]
    RequestHeader set Referer "http://192.168.0.1"
</VirtualHost>

 

I can access the web ui remotely :

  • nat/pat in the MR600 itself,
  • transfer to the reverse-proxy running on Apache
  • back to the WEB UI IP on the MR600
Recommended Solution
  0  
  0  
#2
Options
Re:Error 403 when accessing the WEBUI thru router FQDN or remotely thru Reverse-Proxy
2023-07-31 03:06:45

  @t0urista 

 

Thank you very much for the update, glad to hear that you've solved the problem, which will help to other users as well.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer BE550 New Software Enhances System Stability and Optimizes MLO Network Stability. TL-WA3001 Supports EasyMesh, Speed Limit, Guest Network in AP Mode and/or Multi-SSID Mode. If you found the post or response helpful, please click Helpful. If an answer solves your problem, click "Recommended Solution" so that others can benefit from it.
  0  
  0  
#3
Options