431

Yes that works. Obviously there is a linking problem. In the URL it seems that after the selection the URL is not adjusted correctly - it still remains at `firmware-selector.openwrt.org/?version=22.03.5&...?. If you adjust the version in the URL manually, as suggested, then it works.

For clarification
firmware_selector_raspberryPi4

432

Actually, my suggestion was to simply choose the OpenWrt version from the dropdown before typing your device into the text box. But, yes, editing the URL would also work.

And, yes, it's clearly a bug. The fact that the text box is positioned to the left of the OpenWrt version dropdown naturally encourages the user (if they speak a left-to-right language) to fill in the text box before picking an OpenWrt version, which triggers the bug.

1 Like
433

Good point. A better UX design might be to stack the widgets with the version selector on top, thus making it more natural for everyone, regardless of whether their native language is L-R, R-L or top-to-bottom (are there any that are bottom-to-top? :slight_smile:).

434

It'd be better to just fix the bug. The sequence of which form item is filled out first shouldn't matter.

435

Hi, part of the problem is that the title of the model was changed between OpenWrt versions:

  • "Raspberry Pi 4B/400/4CM (64bit)" (22.03.5)
  • "Raspberry Pi 4B/400/CM4 (64bit)" (SNAPSHOT)

Here is a MR to address some of the problems in the firmware-selector:

3 Likes
436

Actually, it was the intention to have the user fill in the model name first.
The version is usually already set to what is recommended (e.g. latest stable release).

437

Right, but what I'm talking about is when you want a different version. In that case, you have to set the version first, then type the device name, or you will get the error.

438

That will hopefully be fix by the linked MR.

439

4CM to CM4 was very subtle. Good eyes!

440

Xiaomi ax3600 last snapshot image is dated 15/06/2023.... When will the next build take place?

441

You need to select qualcommax, not ipq807x (anymore).

3 Likes
442

Anyone else getting this error when trying to do a custom build?

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

6 Likes
443

Yup, it is the same for me too

1 Like
444

Firmware selector images lagg behind 2-3 days currently, as the packages buildbot seems to not be able to keep up. Many of the packages builds take 5-7 hours and I saw a lot that took more than 14 hours and one that is building since more than a day. I guess this could potentially also cause your problem with the custom builds.

In contrast, the images buildbot seems to run nicely :slight_smile:

1 Like
445

To add to your explanation, unchecking advanced options in ASU showed that the build currently installed was the most recent.

446

same for me

1 Like
447

same for me

1 Like
448

Sysupgrade server has been down since yesterday, so no new builds right now. Don't know how to contact admins...

image
image1273×1134 296 KB

5 Likes
449

You can always run the normal imagebuilder locally, if you need an upgrade now.

450

Somebody reported the issues at OpenWrt's attended sysupgrade server repository: openwrt/asu: Internal Server Error #533. I assume admins monitor this repo.

Edit: the firmware selector is up and running again as of 2023-07-08

1 Like