openwrt / openwrt/openwrt

feeds update failed HTTP 503

Open
#20,510 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
28.5k
Forks
13k
Avg merge
3d 1h
Merged PRs (30d)
160

Description

For three consecutive days, I have reported an error every time I tried to update feeds packages and luci.

Updating feed 'packages' from 'https://git.openwrt.org/feed/packages.git;openwrt-24.10' ...
Cloning into './feeds/packages'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
fatal: the remote end hung up unexpectedly
failed.
Updating feed 'luci' from 'https://git.openwrt.org/project/luci.git;openwrt-24.10' ...
Cloning into './feeds/luci'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
fatal: the remote end hung up unexpectedly
failed.
Updating feed 'routing' from 'https://git.openwrt.org/feed/routing.git;openwrt-24.10' ...
Cloning into './feeds/routing'...
Updating feed 'telephony' from 'https://git.openwrt.org/feed/telephony.git;openwrt-24.10' ...
Cloning into './feeds/telephony'...
Create index file './feeds/passwall_packages.index' 

Related PR
https://github.com/openwrt/openwrt/pull/19881
https://github.com/openwrt/openwrt/pull/19880

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.

Research direction

Start by reviewing the related pull requests at https://github.com/openwrt/openwrt/pull/19881 and https://github.com/openwrt/openwrt/pull/19880, then reproduce the feeds update shown in the report. Determine whether the 503 affects the feed update process or its upstream repositories; done means the affected feeds update without the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.