Many thanks for your help and responses folks! Looks like Stefan, in https://issues.jenkins.io/browse/JENKINS-73760?focusedId=449268&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-449268, caught that this URL was the default URL in ancient times.
Most probably you've inherited the setup across upgrades, which is kept (and not migrated) over Jenkins upgrades while a fresh install uses the new URL (or i missed something else ;) ). => worth switching to the default https://updates.jenkins.io as pointed by Daniel. (I'm still wondering why the redirect is not followed by the internal Java client. Might be the 308 code :thinking:) Le jeudi 12 septembre 2024 à 13:19:10 UTC+2, [email protected] a écrit : > Hi > > On Thu, Sep 12, 2024 at 1:10 PM Damien Duportal > <[email protected]> wrote: > > > > Hi folks, > > > > This is definitively related to our operation > https://www.jenkins.io/blog/2024/09/10/update-center-brownouts-3/. > > > > I'm wondering where would this default HTTP would come from: I just > started up a fresh Jenkins 2.476 from the WAR and it uses the HTTPS by > default (with the "updates.jenkins.io"). > > Are you using a rather old version of Jenkins? Or do you have a custom > UC URL enforced? > > > > The brownout will stop around 02:00pm tonight, but we most probably will > enforce HTTP to HTTPS redirection in the old Update Center VM (as we did > with mirrors 2 years ago). > > > > I do dist-upgrade every release ;). My CI work always with the latest > plugin and jenkins > > Michael > > > > > Cheers, > > > > Damien DUPORTAL, for the Jenkins Infra team > > > > > > Le jeudi 12 septembre 2024 à 09:06:41 UTC+2, [email protected] a > écrit : > >> > >> Hi, > >> > >> saw same issue today and realized that the default url still points to > http. > >> Resetting the url to default value fixed the issue. > >> Maybe there should be a warning / notification if the update center url > points to an old jenkins url (and isn't reachable). > >> > >> Regards > >> Michael > >> > >> [email protected] schrieb am Mittwoch, 11. September 2024 um > 21:01:02 UTC+2: > >>> > >>> On Wed, Sep 11, 2024 at 8:48 PM Michael Nazzareno Trimarchi < > [email protected]> wrote: > >>>> > >>>> Starting to have this problem > >>>> > >>>> java.io.IOException: Could not find JSON in > >>>> > http://updates.jenkins-ci.org/update-center.json?id=default&version=2.476 > >>>> at hudson.model.DownloadService.loadJSON(DownloadService.java:129) > >>> > >>> > >>> Not a dev list question, I recommend you report this to > https://github.com/jenkins-infra/helpdesk/ > >>> > >>> As a workaround I would try replacing the protocol with https, and the > host name with updates.jenkins.io in the plugin manager configuration; > you're still on the default URL from 7+ years ago. > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/6dad3029-90af-4be8-8211-ce112412b963n%40googlegroups.com > . > > > > -- > Michael Nazzareno Trimarchi > Co-Founder & Chief Executive Officer > M. +39 347 913 2170 <+39%20347%20913%202170> > [email protected] > __________________________________ > > Amarula Solutions BV > Joop Geesinkweg 125, 1114 AB, Amsterdam, NL > T. +31 (0)85 111 9172 <+31%2085%20111%209172> > [email protected] > www.amarulasolutions.com > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b27c2dd3-5bb2-4cf9-bb07-edde79707ac6n%40googlegroups.com.
