selector hangs at Received build request and does not deliver firmware
ahh i see its being ddos’ed
yikes
time to wait
always some fool screwing the work of honest people
prolly a script kiddie without nothing to do
or a team of hackers trying to compromise the supply chain.
…and it always starts on Friday evening or Saturday morning, most probably because they somehow know that the man in charge only has time for fixing it on Monday.
it may be a supply chain attack or whatever , its openwrt if they own the firmware selector they own openwrt and all its users cause everyone rely on it, imagine if they get the chain and infect all of us , big botnet, or big data mining or big whatever.
if it were for me i would donate a bunch ton of money to this project but im just a money broke kid.
i highly suggest an “ i’m not a bot “ captcha be implemented on the firmware selector project, that alone will throttle 70% of any spam (possibly), and to make it more simple it could be added below the button request firmware … the simple google captcha can make it and it would not need much work i guess.
How about a queue monitoring feature like this? It shows server status and current queue length from /api/v1/stats.
Demo: https://site-u.pages.dev/www/
Note: The internet connection settings are designed for Japanese ISPs (MAP-E/DS-Lite).
When can nanopi neo4 be supported?
Whoever fixed the https://firmware-selector.openwrt.org - thank you!
Platform support is not part of the Firmware Selector's purpose, you should start a new thread in the Hardware Questions category.
It’s a 4MB flash device (unless you have the B1 version, which is 8MB), so probably not supported for a long time. Though I see it here: https://archive.openwrt.org/releases/22.03.7/targets/ramips/rt305x/ and the build size is around 5MB… which is strange.
There's a project going on right now that is consolidating the downloads site and archives, so the older versions are probably being transitioned and are currently invisible.
SInce I can't see the profiles for that device at present, hard to say why that kmod is (was) being added.
Yes, I have version B1. The last time I built firmware for it was on January 9, 2026.
If I understand you correctly, is there any hope that my model will return to the list of available firmware downloads?
If anyone is interested, there is a project that allows you to build firmware locally.
By the way, I also get an error for the kmod-rt2800-pci package.
Yes, it should reappear on the Firmware Selector. It's already accessible via auc and LuCI ASU, so the data is in place, but the FS is currently throwing CORS errors for some versions. Looking into it...
Cross-Origin Request Blocked: The Same Origin Policy disallows reading
the remote resource at
https://downloads.openwrt.org/releases/22.03.7/.overview.json.
(Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
For those on snapshot (un)attended upgrades, the latest removes dnsmasq by default.
