Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CORS NOT ACCEPTING LOCALHOST

Open
#568 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
next.js
Domain
api

Research direction

The report identifies no repository file, test, or entry point; begin by reproducing the ethers request from a Next.js localhost:3000 client against relay-sepolia.flashbots.net and checking whether the issue belongs in this documentation repository. Done is not defined by the issue; the affected behavior or its documented limitation would need to be confirmed.

Written by the indexing model from the issue text.

Description

When I tried to do simulate with the ethers client, my request got blocked by cors on sepolia relay.
I was using it on next.js.

Access to fetch at 'https://relay-sepolia.flashbots.net/' from origin 'http://localhost:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
Dominant language
TypeScript
Stars
245
Forks
198
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from flashbots/flashbots-docs

All issues in flashbots/flashbots-docs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.