This article describes how to access the J-web from an interface behaves if it's not included under  "system services web-management"

Assume J-web is enabled on an interface say reth0.0. If the user tries to open the J-web (using reth0.0 ip address), from a remote end and the packets enter the device through a different interface, say st0.0, the error "Access Error 403 Forbidden" will be seen on the browser.

 Assume J-web is enabled on an interface say reth0.0.  If the user tries to open the J-web (using reth0.0 ip address), from a remote end and the packets enter the device through a different interface, say st0.0, the error "Access Error 403 Forbidden" will be seen on the browser.

root@host# show system services web-management
http {
       interface reth0.0;
}

Even though the user tries to access j-web using the ip address of reth0.0 interface, the packets reach the device through st0.0. In that case, http server on the device does not accept the packets and returns the 403 error to the client. This is by design. To make it possible to access the j-web, interface st0.0 has to be added to the web-management interface list.

root@host# show system services web-management
http {
        interface [ reth0.0 st0.0 ];
}


 

2020-07-18: Archived.