# Jenkins version 2.498 cksum is invalid

**URL:** <https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198>\
**Category:** Community\
**Created:** [February 19, 2025, 7:33pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198 "2025-02-19T19:33:49Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 7:33pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/1 "2025-02-19T19:33:49Z")

</div>

Says it should be c620cca3c55f1a0441ca04ff7f41696d7057a185ebb63d6d09c182421c8cba8e but is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Potentially corrupted release artifact - should be rolled back immediately

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 7:34pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/2 "2025-02-19T19:34:26Z")

</div>

To validate download [https://updates.jenkins.io/download/war/2.498/jenkins.war](https://updates.jenkins.io/download/war/2.498/jenkins.war)  
sha256sum jenkins.war e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Causing war file to seem corrupted

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [February 19, 2025, 8:01pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/3 "2025-02-19T20:01:41Z")

</div>

I can’t duplicate the problem that you’re reporting. You’ll need to provide more details so that others can duplicate it.

The [mirrorlist for Jenkins latest weekly](https://updates.jenkins.io/latest/jenkins.war?mirrorlist) and the [mirrorlist for Jenkins 2.498](https://updates.jenkins.io/download/war/2.498/jenkins.war?mirrorlist) both show the correct SHA-256 checksum. The file that I download from my nearest mirror provider shows the correct value:

 ![mirrorlist](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/c/ca893160d76c8f06e5f442f0e6ec147d9b8bf177.png)

It is a little surprising the SHA-256 checksum that you share in your message `e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855` is the same checksum referenced in a [2021 issue report](https://github.com/jenkinsci/docker/issues/1212) to the Jenkins docker container repository. I don’t have any reason why that same checksum would appear in a 2021 issue report about git LFS and in your download.

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:03pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/4 "2025-02-19T20:03:00Z")

</div>

Yep - apologies  
Believe I jumped to conclusions here and the issue is somewhere on my end

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:32pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/5 "2025-02-19T20:32:59Z")

</div>

@MarkEWaite figured it out - [https://updates.jenkins.io/stable/latest/jenkins.war](https://updates.jenkins.io/stable/latest/jenkins.war)  
Is pointing to [https://updates.jenkins.io/dynamic-stable-2.492.1/latest/jenkins.war](https://updates.jenkins.io/dynamic-stable-2.492.1/latest/jenkins.war)

Which is invalid now

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:42pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/6 "2025-02-19T20:42:11Z")

</div>

converting to useing [Index of /download](https://updates.jenkins.io/download/)  
Path corrected the issue

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [February 19, 2025, 8:44pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/7 "2025-02-19T20:44:26Z")

</div>

> [@cs166068](#):
>
> figured it out - [https://updates.jenkins.io/stable/latest/jenkins.war](https://updates.jenkins.io/stable/latest/jenkins.war)

What suggested that you should use that URL to download a Jenkins release? I’m not aware of any location that suggests that /stable/latest/ is a valid location for Jenkins downloads. If there is such a location, we want to correct it.

The Jenkins download page includes the link [https://get.jenkins.io/war-stable/2.492.1/jenkins.war](https://get.jenkins.io/war-stable/2.492.1/jenkins.war) for the LTS version and it includes the link [https://get.jenkins.io/war/2.498/jenkins.war](https://get.jenkins.io/war/2.498/jenkins.war) for the weekly version.

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:46pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/8 "2025-02-19T20:46:30Z")

</div>

> **[{{ title }}](https://updates.jenkins.io/download/war/)**
>
> {{ description }}

This points you to it

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:46pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/9 "2025-02-19T20:46:59Z")

</div>

[https://updates.jenkins.io/download/war/[https://updates.jenkins.io/download/war/](https://updates.jenkins.io/download/war/)](https://updates.jenkins.io/download/war/%5Bhttps://updates.jenkins.io/download/war/%5D(https://updates.jenkins.io/download/war/))

I found it taking over the jenkinsapi python package

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:47pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/10 "2025-02-19T20:47:49Z")

</div>

Got there via

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/4/4142e28f5fadd6b46700af90c203f9ca3d693ab7.png)  
as well googling jenkins war download

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 8:54pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/11 "2025-02-19T20:54:27Z")

</div>

@MarkEWaite whats interesting is this worked until around yesterday

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [February 19, 2025, 9:47pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/12 "2025-02-19T21:47:36Z")

</div>

I don’t see a reference to **/stable/latest/** anywhere in any of the references that you provided. Can you provide a more precise reference?

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 10:05pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/13 "2025-02-19T22:05:21Z")

</div>

[https://get.jenkins.io/war/latest/](https://get.jenkins.io/war/latest/)

---

<div class="post-metadata">

**Author:** ![cs166068](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/cs166068/32/7784_2.png) [@cs166068](https://community.jenkins.io/u/cs166068)\
**Post date:** [February 19, 2025, 10:09pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/14 "2025-02-19T22:09:18Z")

</div>

All usages appear resolved - old file url is working again  
I almost can’t believe nothing changed on your side

---

<div class="post-metadata">

**Author:** ![danielbeck](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/danielbeck/32/89_2.png) [@danielbeck](https://community.jenkins.io/u/danielbeck)\
**Post date:** [February 19, 2025, 10:16pm UTC](https://community.jenkins.io/t/jenkins-version-2-498-cksum-is-invalid/27198/15 "2025-02-19T22:16:21Z")

</div>

> [@MarkEWaite](#):
>
> It is a little surprising the SHA-256 checksum that you share in your message `e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855` is the same checksum referenced in a [2021 issue report](https://github.com/jenkinsci/docker/issues/1212) to the Jenkins docker container repository.

It’s not.

```auto
echo -n '' | sha256sum 
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 -
```
