Server maintenance 18.07.2024

[aparcar]

For whatever reason the server is acting up as in not propagating the right versions. I'm investing please wait before reporting any issues.

[aparcar]

Good old podman system reset --force fixed the issues, for some reason the containers DNS resolution wouldn't work anymore.

[aparcar]

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

[figgelus]

Any progress? firmware selector still down at 19/7 11:00 UTC+2

[fsa]

Unfortunate coincidence. I need to update urgently, as there is a bug in firmware 23.05.3 and my NAT64 is not working and the update is not available.

[jalexvig]

Looks like builds are now working but not downloads

[aparcar]

I tested firmware selector, AUC and OWUT, all working as expected. Docker lagging issues may appear due to our CI being bloated with kernel builds, that's another mission for another day.

[jalexvig]

@aparcar Would this cause the 404s seen on download links?

[jalexvig]

Ah looks like it's just cached build download links that 404 - I just added an extra package for a custom build and it works fine.

[aparcar]

Yes there was a problem with the path, should be fixed

[maurice-w]

Firmware selector does indeed work for me, but still no luck with luci-app-attendedsysupgrade. Am I missing something?

[fsa]

It's likely that you've already requested the build you need before. For such assemblies, 404 is still issued. I had to change one package on the site and then I got a working firmware. And through luci it also gives an error.

[maurice-w]

Never mind, I found #896. It works with auc.

[udanfacy22]

Neither auc nor luci-app-attendedsysupgrade work for me.

luci-app-attendedsysupgrade gives me the same {"detail":"Not Found"} error that others mentioned.

auc gives me this output:

auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org
Running:   23.05.3 r23809-234f1a2efa on bcm27xx/bcm2711 (raspberrypi,4-model-b)
Invalid argument (22)

---

Update: Fortunately, using the firmware-selector, I was able to successfully build 23.05.4 with custom packages. After successfully upgrading that way, I can now report that this problem has not gone away in 23.05.4. Luci-app-attendedsysupgrade and auc still generate the same error messages that they did in 23.05.3.

[aparcar]

Thanks for testing and feedback, I'll try to give this another go tonight

[devastgh]

As of now, auc upgrading to 23.05.4 doesn't work on my x86/64 devices. Luci app same story.

root@HAWAII:~# auc -c
auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org/
Running:   23.05.3 r23809-234f1a2efa on x86/64 (generic)
No data available (61)

[aparcar]

@devastgh i can't reproduce the issue

[devastgh]

@devastgh i can't reproduce the issue

I upgraded my x86/64 boxes manually from firmware selector, however auc still fails there even on 23.05.4:

root@HAWAII:~# auc -c
auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org/
Running:   23.05.4 r24012-d8dd03c46f on x86/64 (generic)
No data available (61)

root@PENTAGON:~# auc -c
auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org/
Running:   23.05.4 r24012-d8dd03c46f on x86/64 (generic)
No data available (61)

Both devices are dual stack, so connection is probably ipv6 to the servers.

My ipv4 only AX3000T devices work properly:

root@Bahamas:~# auc -c
auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org
Running:   23.05.4 r24012-d8dd03c46f on mediatek/filogic (xiaomi,mi-router-ax3000t)
Available: 23.05.4 r24012-d8dd03c46f
Requesting package lists...
 luci-mod-network: git-24.111.76511-ff6b275 -> git-24.207.52553-1f36628

I have absolutely no clue what the issue could be here.

[devastgh]

I have absolutely no clue what the issue could be here.

Found the issue. I had https://sysupgrade.openwrt.org/ in the config instead of https://sysupgrade.openwrt.org . It doesn't like the trailing slash in the url. Sorry for the confusion there.

[lpic10]

Found the issue. I had https://sysupgrade.openwrt.org/ in the config instead of https://sysupgrade.openwrt.org . It doesn't like the trailing slash in the url. Sorry for the confusion there.

It's been weeks I'm trying the update and that did the trick.

Something has changed on server side that is causing this issue as I never changed the config, so I believe that was coming as default (at least on previous builds).

I think it would be better to find a solution server side, as a lot of other users may not find this info here.

[aparcar]

I think it would be better to find a solution server side, as a lot of other users may not find this info here.

Should be fixed via #936

[hainguyen-cmd]

@aparcar: Is there any problem? I have tried to customize firmware with selected packages through https://firmware-selector.openwrt.org but can not! The error is:

index.js:118

   POST https://sysupgrade.openwrt.org/api/v1/build net::ERR_ABORTED 502 (Bad Gateway)

Thanks.

[SebTM]

Same issue as @hainguyen-cmd, also reported in matrix (https://matrix.to/#/!UDNBKbeuCquyiBFFzO:matrix.org/$v3LaiIZJEqSKjt7c5it73soRsEwG4wDkPaPRockkMWU?via=matrix.org&via=lodere.es&via=matrix.ipv8.pl)