codesandbox / codesandbox/codesandbox-client

403 Access denied on fresh install of dependency

Open
#8,889 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

There is a duplicate issue from 2023. still creating a new issue because I cannot judge if and how they are related.

Description of the problem

once i added @tributary-so/sdk-react to the package.json, the preview (and site) stopped working.

site: https://npj58s.csb.app/

GET https://prod-packager-packages.codesandbox.io/v2/packages/@tributary-so/sdk-react/1.6.6.json gives a 403 with:

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>5KP4BJEEP970SH2X</RequestId><HostId>TDh996zDeVP/zyntYuH5fQyzQ4fflemlHrAkVTBeZ4VXCx6Kf97CSj/D33qT69+AkEhLSDAZhIw=</HostId></Error>

How has this issue affected you? What are you trying to accomplish?

Cannot proceed. Get a white-screen-of-death

To Reproduce

Just open: https://npj58s.csb.app/

Link to sandbox: link
Your Environment
Software Name/Version
Сodesandbox
Browser Firefox
Operating System ArchLinux

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 linked sandbox and inspect the package.json entry for @tributary-so/sdk-react. Then trace the request to the prod-packager-packages.codesandbox.io endpoint and compare it with issue #7920. Done means a fresh install can load the preview and site without the 403 response or white screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.