RocketChat / RocketChat/Rocket.Chat

BUG: CDN Download Link for 7.10.8 (.tgz) returns AccessDenied

Open
#39,466 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

The official CDN download link for the Rocket.Chat 7.10.8 release (tarball) is returning an AWS AccessDenied error. It appears the .tgz object was uploaded to the S3 bucket without the correct public-read permissions, preventing community users who use manual/tarball deployments from downloading the latest security patch.

Steps to reproduce:
  1. Navigate to the release URL: https://releases.rocket.chat/7.10.8 (or use wget/curl).
  2. Follow the redirect to the CDN: https://cdn-download.rocket.chat/build/rocket.chat-7.10.8.tgz
  3. Observe the AccessDenied XML error instead of the file downloading.

(Note: Attempting to download older versions, such as https://cdn-download.rocket.chat/build/rocket.chat-7.10.2.tgz, still works perfectly).

Expected behavior:

The rocket.chat-7.10.8.tgz archive should download successfully so server administrators can apply the update.

Actual behavior:

The CDN returns a 403 Forbidden / AccessDenied error from Amazon S3.

Server Setup Information:
  • Version of Rocket.Chat Server: Attempting to install 7.10.8
  • License Type: Community
  • Number of Users: N/A
  • Operating System: N/A (Infrastructure Issue)
  • Deployment Method: tar
  • Number of Running Instances: N/A
  • DB Replicaset Oplog: N/A
  • NodeJS Version: N/A
  • MongoDB Version: N/A
Client Setup Information
  • Desktop App or Browser Version: Any browser, curl, or wget
  • Operating System: Any
Additional context

Because 7.10.8 contains a security patch, this broken infrastructure link is preventing users who rely on tarball deployments from securing their servers. The Docker image pulls fine, so this appears to be strictly an S3 object permission/ACL issue on the CDN bucket for this specific release.

Relevant logs:
<Error>
    <Code>AccessDenied</Code>
    <Message>Access Denied</Message>
</Error>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the 7.10.8 release URL or the CDN URL using curl or wget, and compare it with the working 7.10.2 archive. Inspect the release CDN/S3 configuration for the 7.10.8 object; done means the tarball downloads successfully without AccessDenied.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.