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

老是报:unexpected status 503 Service Unavailable: OpenCodex inbound request body capacity is temporarily exhausted. Retry after the current request completes., url: http://127.0.0.1:10100/v1/responses

Closed
#6,793 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript

Research direction

Search the repository for the 503 message 'inbound request body capacity is temporarily exhausted' and for the config keys maxInboundBodyBytes, maxUpstreamBodyBytes and appOwnedMemoryBudgetMb to find where the inbound body budget is enforced for the /v1/responses route. Reproduce by sending several image-bearing requests to that route and watching when the budget is released. Done means multi-image conversations no longer return 503 under the default configuration, with a test covering the release path.

Written by the indexing model from the issue text.

Description

bug platform service
Client or integration

Codex App

Area

Platform (Windows / macOS / Linux)

Summary

开了一个对话,生成了3张图,就开始报这个错。我的Win0 16GB内存之前都是好的,账号没问题,现在频繁报错,都影响到正常项目了,只能先不用了,用直连。这个能不能直接看看怎么解决?这是 Open Codex 的问题

Reproduction

ocx service restart
ocx restart
有时候有用,没两句对话又出来了

Version

2.8

Operating system

Windows 10

Provider and model

codex

Logs or error output
unexpected status 503 Service Unavailable: OpenCodex inbound request body capacity is temporarily exhausted. Retry after the current request completes., url: http://127.0.0.1:10100/v1/responses
Screenshots and supporting files
Image
Redacted configuration
config.json 都加了这些设置了,也没有用:
"managementUsageMaxReadBytes": 67108864,
  "maxUpstreamBodyBytes": 134217728,
  "maxInboundBodyBytes": 536870912,
  "appOwnedMemoryBudgetMb": 512,
Checks
  • I searched existing issues and documentation.
  • I removed secrets, tokens, account details, request credentials, and personal data.
Dominant language
TypeScript
Stars
16.9k
Forks
1.3k
Avg merge
8h 20m
Merged PRs (30d)
672

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 lidge-jun/opencodex

All issues in lidge-jun/opencodex

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.