Just worked for me. What OpenWrt version?
@efahl Downloading any custom built firmwares doesn't work for several days now. The FS builds the image when requesting a custom firmware, but can't download it - the browser just loads and loads, but can't get the file to my PC.
Interestingly enough, the alternate github.io FS works just fine https://openwrt.github.io/firmware-selector-openwrt-org/
Ok, just tested for 24.10.1 x86/64 and it did a build then download just fine. Is it still failing for you? Could it be a browser issue???
Yeah, it seems like it's a browser issue, indeed. It only occurs in Firefox, but not in Chrome, for any custom SNAPSHOT build request. I'll clear the Firefox cookies/cache and check again...
The coding here is pretty bad and has been for quite a while, there are unhandled promise rejections:
Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Edit: And now it doesn't work at all. I press on Request Build and nothing happens. Man, is this bad...
That's in the FS javascript? Could you post a traceback, I'll see if I can figure out what's up with it.
Can't reproduce it right now. It wasn't working for a while, now it's back to the main issue, where I can't download the built image with Firefox. So, after the build is finished, it throws this error:
and the Console logged a CORS error:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://sysupgrade.openwrt.org/api/v1/build/0e19dd41711d5e926bc689c9ca0e8229f94f120dedc4edd006f9b55fa8b0a35a. (Reason: CORS request did not succeed). Status code: (null).
I already cleared the cookies/data/cache whatever else, but it didn't help.
It looks like you run the firmware-selector yourself. For ASU you need to allow Cross-Origin Requests in your browser. It is not related to cookies/data/cache.
No, I'm actually loading and using https://firmware-selector.openwrt.org in Firefox. The issue doesn't seem to occur in Chrome. Do you think it's due to me using the Avast antivirus? I know it behaves as a man-in-the-middle service in browsers.
But then, why is https://openwrt.github.io/firmware-selector-openwrt-org/ working perfectly fine in the same Firefox browser?
Edit: Reinstalled Avast, problem seems to be fixed.
1 Like
Hello everyone. I am trying to download custom image for FritzBox 7412 (lantiq/xrx200) from firmware selector (version 24.10.1). But it does not work. It says "init". Nothing else happens. I tried Chromium and Firefox, same result. 24.10.0 works properly. Should i report a bug somewhere? Thank you in advance!
That combination is broken, you'll need to pick a different version. If you're already on 24.10.0, I'd just wait for 24.10.2 to come out, shouldn't be too long...
1 Like
Broken again... when choosing SNAPSHOT it throws the error:
Failed to execute 'json' on 'Response': Unexpected end of JSON input
Edit: Seems to be fixed.
1 Like
Yeah, I've been seeing this for a couple of days, too, but it's very transient. I get an error trying to do a build, try running the build container standalone and see it's an issue with the keys, then a bit later everything works...
Reported on https://github.com/openwrt/docker/issues/176
1 Like
Hey @efahl, since you're the go-to guy for anything and everything having to do with updates, I was wondering if you could fix a particularly puzzling behavior: Every few days, the version numbers of most (but not all) Luci packages increment, even if there is no change. No other packages do this.
In fact, Luci didn't do this until a few months ago, so it appears to be a deliberate decision. It seems utterly mad to keep updating the version number when nothing has actually changed. At the very least, the version should be frozen for stable releases. Again, even in snapshot, other packages don't do this.
I believe it is due to dependencies changing. Look at https://github.com/efahl/luci/blob/affbd1be0c8915adad116ca1f7162b36eeaffafb/modules/luci-base/Makefile#L16 Whenever any of those change, then it likely triggers a build of luci-base, which in turn fires off builds of all luci-app-*s that depend on it.
I don't see anything that's changed in the luci repo build scripts or Makefiles that would cause an increase in builds, so it might be a coincidence that you started noticing it recently. I know that rpcd and ucode have had a lot of changes committed recently, where they've been fairly stable for a while previously. Also there have been a lot of translation file changes, so the language packs are being committed/built fairly frequently.
I installed some old versions to figure this out. As late as 24.10.0, all the luci packages have their own build number. Starting with 24.359, they become aligned and updated roughly every three days. Stable builds should be uh, stable, and not constantly refreshed.
One way to easily visualize this is to look at the laughably long directory at https://archive.openwrt.org/releases/24.10.2/packages/x86_64/luci/ compared to say, https://archive.openwrt.org/releases/22.03.7/packages/x86_64/luci/
Maybe there was a good rationale for this change when it occurred, but the unintended consequences seem highly undesirable to me.
Would it be possible to add the option to enable multiple features that are only available if you make your own build?
Stuff like Open NAT, Enable CONFIG_NO_HZ_FULL and CONFIG_PREEMPT=y
That is only possible using the SDK and Image Builder tools from downloads.openwrt.org
If you can customize installed packages, i`m sure they can make it so you can also be able to enable extra features.
No, those specifically require recompilation and the imagebuilders don't do any compilation. They simply take already-compiled kernels, rootfs and packages, then do package installs and creation of imgs.
3 Likes