23.05.4 is not released. You should not try to use it until it is officially announced.
1 Like
Is there anyone got problem when doing customize build (Customize installed packages and/or first boot script) on OpenWRT Firmware Selector?
I have tried but got problem (as in attached image).
@aparcar is doing maintenance on the ASU server: https://github.com/openwrt/asu/issues/663#issuecomment-2235843620
A new round, I'll have to reconfigure multiple things,
server is down until further notice, should be done by tomorrow.
Sorry for the inconvenience
3 Likes
Thanks so much! Now I have new way to check before asking 
23.05.4 a choice on the firmware selector right now.
Yes, but don't try to use it until 1) it has been officially announced, 2) the ASU server backend for the Firmware Selector is working.
How do I use the ASU server backend? Or know if it's working?
My link goes to the, "OFS %GIT_VERSION%"
How do I go to the "ASU Server Backend?"
Usually, you use the Attended SysUpgrade server by running one of its clients, which are as far as I know these four:
- Firmware Selector - this thread, so no explanation needed.
- LuCI Attended Sysupgrade app - the web based client that you install on your router.
auc- a command line client that does the same, available in OpenWrt since ~2018 through 23.05.owut- new command line client that replacedaucin snapshot, and future releases (24.x and later).
Lots of details here
- LuCI ASU and
auc: https://openwrt.org/docs/guide-user/installation/attended.sysupgrade owut: https://openwrt.org/docs/guide-user/installation/sysupgrade.owut
Or, you could use the ASU server directly, as I hint in this post. (There are a lot of details glossed over in that, but feel free to ask about it there.)
Aye, there's the rub. As you are keenly aware, the chain of events leading from source code to a router upgrade is long and complicated, so lots of things can break along the road and it's often hard to pinpoint where it all goes wrong.
First, the buildbots have to create their build artifacts and upload them to https://downloads.openwrt.org/.
Second, ASU server has to monitor those builds, and at the proper time, extract information from them (version numbers, package lists, all that stuff). You can see an overview at https://sysupgrade.openwrt.org/, but to answer your question "is it working?" you have to dig deeper. Looking at its static data in https://sysupgrade.openwrt.org/json/v1/ sometimes can tell us, as the starting point for the router-based clients is the overview.json, if it's missing, nothing can proceed.
Firmware Selector, on the other hand, does its own metadata harvesting, so if the ASU server's metadata harvesting fails, then FS can still work, and vice versa, so that's confusing.
Or, start surfing through the directories there, and see if there are missing files (which of course assumes you know what should be there, and that's impossible for almost everyone). For example, I know there should be a packages directory under https://sysupgrade.openwrt.org/json/v1/snapshots/ (the ASU server is broken right now, so it's not there), but how would anyone else know this?
Third, and most important to FS is that ASU server also provides a builder backend using the imagebuilder artifacts from the first step, above. All clients use this component, but they all use it a bit differently, which is why sometimes an upgrade with FS fails, but one using the LuCI app will succeed.
Given that shortish (for me) wall of text, the only answer I can come up with is
Q: "How do I know if ASU server is working?"
A: "Try an upgrade and see if it works..."
(Alternatives, use imagebuilder, SDK or source builds.)
Finally, an easy one 
: https://sysupgrade.openwrt.org/
Look at the API link and you can probably figure out some of the functionality the server provides, most notably the "build request" which is what FS is using to create the custom images. (Oho, I just went there and that's broken, too.)
And, as always, for The Hardcore™ just read the code: https://github.com/openwrt/asu/
4 Likes
Wow. Great reply. Bookmarked. Thanks!
I got the email announcing it, went to the Firmware Selector and successfully created a build to download, but no joy. I get this message clicking on either factory or sysupgrade download boxes.
Is it just me or maybe the big outage today has something to do with it? Or what? What should I be checking on my end?
Yeah, lots of reports coming in that the ASU server is still a bit shaky for various platforms. I'm ok on ath79, and sort of ok on x86 (it's missing libusb-1.0), but on mediatek is borking out completely. I'm going to wait a couple days for the dust to settle.
1 Like
setting " uci-defaults" on ath79 / ramips / mediatek is rejected with red:
Handling
'defaults'not enabled on server
for all 23.05. xx and snapshot
1 Like
Known issues
- lantiq/xrx200 target shows error messages in DSA switch configuration of the integrated GSWIP switch. (see: #13200)
So I guess lantiq/xrx200 is and will be supported only in snapshots (kernel 6.6), see https://github.com/openwrt/openwrt/pull/15811
i don't think so. because there is 23.05.4 image for Zyxel 2812. also I can compile from git. so, I wonder why is this happening?
Like 5 days with this issue .... I tried to add some package to openwrt image after that when I try to download it ...i got this error
Getting the same here. Very frustrating when adding a script comment is the only workaround for bypassing the build caching which can deliver week-old snapshots.
1 Like
getting the same
This appears to be resolved now, fortunately. 
2 Likes