Two Jenkins Linux instances both running Jenkins ver. 2.77 but Manage Plugins "Check now" button behavior is different between the two

[Raye Raskin]

I started out with one instance at a LTS version, the other instance at a more recent version. Don't remember the exact versions. I've been keeping up to date as new versions are available for each instance. A while back both instances were updated to the same version.

Anyway, in instance A when I click the "Check now" button I get a screen update in about 4 or so seconds with a list of any available plugin updates or Jenkins updates. Fine.

In instance B when I click the same "Check now" button I get "Checking Updates..." which eventually changes to "Checking Updates... Done" at which point I have to click "Go back to update center".

How do I get instance B to behave like instance A?

[Daniel Beck]

> On 7. Sep 2017, at 18:13, 'Raye Raskin' via Jenkins Users <jenkins...@googlegroups.com> wrote:
>
> Anyway, in instance A when I click the "Check now" button I get a screen update in about 4 or so seconds with a list of any available plugin updates or Jenkins updates. Fine.
>
> In instance B when I click the same "Check now" button I get "Checking Updates..." which eventually changes to "Checking Updates... Done" at which point I have to click "Go back to update center".
>
> How do I get instance B to behave like instance A?

Compare the options for 'browser-based metadata download' in the security settings between the two instances.

[Raye Raskin]

Exactly! You nailed it. Thank you!