This article describes the issue of the switch not being accessible via J-Web, but reachable via SSH or Telnet services.

Unable to access the EX switch via J-Web, but able to access the switch via SSH or Telnet.

For a J-Web Issue, before you start troubleshooting, check the following parameters:

• Whether the user is able to ping the switch IP (RVI/L3/Management) from their PC.

• Clear the browsing data ( cookies/ temporary internet files/ misc cache ) on the browser and check again.

• Try a different browser and check again.

•  Check if the PC is directly connected to the Management interface (same VLAN) or the PC is in a different VLAN.

• Try a different PC. Make sure its not a built-in or third party firewall issue on the PC.

• To further isolate the issue, ask the user to connect a laptop directly to the management interface.

• If the management interface is not configured, then connect the PC directly to the switch port of the same VLAN, on which the IP is configured for L3 access.

• Try to login via HTTP, check the log messages, and look for any reported error.

• Try to login, check the httpd.log file, and look for any reported error; for example:
  

  user@switch#run show log httpd.log

• Make sure that no firewall is configured on the EX to block HTTP traffic. Check the configuration and see if there is anything that could block HTTP.

1. Identify the PID for the http and httpd-gatekeeper daemons:
   

   user@switch% ps -aux | grep http
   root 870 0.0 0.2 6312 2060 ?? S 10:20PM 0:00.04 /usr/sbin/httpd-gk -N
   nobody 1903 0.0 0.3 6880 2924 ?? S 9:09AM 0:00.04 /packages/mnt/jcrypto-ex/usr/sbin/httpd -N
   root 1905 0.0 0.1 2084 784 p0 R+ 9:09AM 0:00.01 grep http

2. Use the Kill -9 shell command to kill both httpd and httpd-gk .

• Check if J-Web is accessible.

• Delete the HTTP service from the device and commit:
  

  user@switch# delete system services web-management
  user@switch# commit force (Type force in full, as this is a hidden command)

• Configure the HTTP service:
  

  user@switch# set system services web-management http
  user@switch# commit force     (Type force in full as this is a hidden command)

• Check if J-Web is accessible. If J-Web is still inaccessible, check if it is accessible via HTTPS.
• If J-Web is accessible via HTTPS, but not via HTTP, then switch the mastership and check (in case of virtual chassis):
  

  user@switch# run request chassis routing-engine primary switch

• If J-Web is accessible via HTTP after the switchover, then revert to the previous primary and check again if access is possible via HTTP.