Junos OS

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

Hi Cliff,

have you also installed the jweb for your SRX? And do you have a loopback-interface?

Starting with Junos OS Release 25.2R1, the Junos bundle for SRX Series Firewalls includes jweb-srx-app as an optional package. You must use the CLI to install the J-Web SRX Application Package.

1. Once the loopback interface is configured, run the following command:

   root>request system software add optional://jweb-srx-app

2. To reboot your device to install the package successfully, run the following command:

   For a VM host device: root>request vmhost reboot

   For a non VM host device: root>request system reboot

   NOTE:

   Reboot is mandatory for successful installation of J-Web SRX Application Package.

   https://www.juniper.net/documentation/us/en/software/jweb-srx25.2/jweb-srx/topics/topic-map/j-web-security-starting.html

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

I didn't get the sequence quite right. I entered

> request system software add optional://jweb-srx-app

# set interfaces lo0 unit 0 family inet address 127.0.0.1/32

# commit

> request system reboot

Now I can access the web login page. I can enter my username and password. After that, I get a spinning wheel forever. When I refresh the page, the session has expired.

My only access is by console cable or PuTTY. I'm not terribly experienced with Juniper CLI. That is why I prefer GUI.

Hi Cliff,

have you also installed the jweb for your SRX? And do you have a loopback-interface?

Starting with Junos OS Release 25.2R1, the Junos bundle for SRX Series Firewalls includes jweb-srx-app as an optional package. You must use the CLI to install the J-Web SRX Application Package.

1. Once the loopback interface is configured, run the following command:

   root>request system software add optional://jweb-srx-app

2. To reboot your device to install the package successfully, run the following command:

   For a VM host device: root>request vmhost reboot

   For a non VM host device: root>request system reboot

   NOTE:

   Reboot is mandatory for successful installation of J-Web SRX Application Package.

   https://www.juniper.net/documentation/us/en/software/jweb-srx25.2/jweb-srx/topics/topic-map/j-web-security-starting.html

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

I didn't get the sequence quite right. I entered

> request system software add optional://jweb-srx-app

# set interfaces lo0 unit 0 family inet address 127.0.0.1/32

# commit

> request system reboot

Now I can access the web login page. I can enter my username and password. After that, I get a spinning wheel forever. When I refresh the page, the session has expired.

My only access is by console cable or PuTTY. I'm not terribly experienced with Juniper CLI. That is why I prefer GUI.

Hi Cliff,

have you also installed the jweb for your SRX? And do you have a loopback-interface?

Starting with Junos OS Release 25.2R1, the Junos bundle for SRX Series Firewalls includes jweb-srx-app as an optional package. You must use the CLI to install the J-Web SRX Application Package.

1. Once the loopback interface is configured, run the following command:

   root>request system software add optional://jweb-srx-app

2. To reboot your device to install the package successfully, run the following command:

   For a VM host device: root>request vmhost reboot

   For a non VM host device: root>request system reboot

   NOTE:

   Reboot is mandatory for successful installation of J-Web SRX Application Package.

   https://www.juniper.net/documentation/us/en/software/jweb-srx25.2/jweb-srx/topics/topic-map/j-web-security-starting.html

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

I would use a console cable and plug a laptop in to see what changed and what the message log shows. 

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?

I did compare the current config to the last saved. No changes.

I would use a console cable and plug a laptop in to see what changed and what the message log shows. 

I updated my SRX-340 to firmware version 25.2R1.0 in July.

Don't recall accessing the SRX since. Now in October, when I try to login via the webpage, I receive the notice that the device refuses to connect. I'm trying to connect through the Management port.

I can ping the admin address.

I obviously had access in July. What may have changed?