ASUS BIOS route not working

[b9AcE]

Routes

/asus/bios/:model

Full routes

/asus/bios/ProArt-X670E-CREATOR-WIFI

Related documentation

https://docs.rsshub.app/routes/program-update#bios

What is expected?

The source website should be checked for updated content and if so convert it to RSS.

What is actually happening?

No response from the source webserver (https://odinapi.asus.com.cn).

Deployment information

Self-hosted

Deployment information (for self-hosted)

DietPi v9.7.1, Docker version 27.2.1, image: diygod/rsshub:chromium-bundled

Additional info

RSSHub's log says rsshub-1 | error: Request https://odinapi.asus.com.cn/recent-data/apiv2/SearchSuggestion?SystemCode=asus&WebsiteCode=cn&SearchKey=ProArt-X670E-CREATO R-WIFI&SearchType=ProductsAll&RowLimit=4&sitelang=cn fail: TypeError: fetch failed.
The server https://odinapi.asus.com.cn in https://github.com/DIYgod/RSSHub/blob/master/lib/routes/asus/bios.ts is indeed entirely inaccessible and has been so at least since mid-August.
It may (or may not) be some geoIP-blocking which does not allow visitors from IP-addresses registered to Europe. It seems reasonable either way that the route should instead use the global website, or if that is inaccessible to people in China at least have one route for people in China and one for the rest of the world, so that the above example would then instead be https://odinapi.asus.com/recent-data/apiv2/SearchSuggestion?SystemCode=asus&WebsiteCode=us&SearchKey=ProArt-X670E-CREATOR-WIFI&SearchType=ProductsAll&RowLimit=4&sitelang=en for example, which is accessible.

This is not a duplicated issue

• I have searched existing issues to ensure this bug has not already been reported

[github-actions]

Searching for maintainers:

• /asus/bios/:model: @Fatpandac

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。

[b9AcE]

I don't know if I'm missing something here, but it does not seem to have worked?
After with the image: diygod/rsshub:chromium-bundled in my docker compose file running docker compose down && docker compose pull && docker compose up -d && docker compose logs -f and then as a test wget -- 'http://localhost:1200/asus/bios/ProArt-X670E-CREATOR-WIFI/en' I still get errors like this:

rsshub-1  | info: <-- GET /asus/bios/ProArt-X670E-CREATOR-WIFI/en
rsshub-1  | error: Request https://www.asus.com.cn/support/api/product.asmx/GetPDBIOS?website=cn&model=ProArt-X670E-CREATOR-WIFI&pdid=20995&sitelang=cn fail: TypeError: fetch failed
rsshub-1  | error: Request https://www.asus.com.cn/support/api/product.asmx/GetPDBIOS?website=cn&model=ProArt-X670E-CREATOR-WIFI&pdid=20995&sitelang=cn fail: TypeError: fetch failed
rsshub-1  | error: Request https://www.asus.com.cn/support/api/product.asmx/GetPDBIOS?website=cn&model=ProArt-X670E-CREATOR-WIFI&pdid=20995&sitelang=cn fail: TypeError: fetch failed
rsshub-1  | error: Error in /asus/bios/ProArt-X670E-CREATOR-WIFI/en: FetchError: [GET] "https://www.asus.com.cn/support/api/product.asmx/GetPDBIOS?website=cn&model=ProArt-X670E-CREATOR-WIFI&pdid=20995&sitelang=cn": <no response> fetch failed
rsshub-1  | info: --> GET /asus/bios/ProArt-X670E-CREATOR-WIFI/en 503 33s

Latest tested just <5 minutes ago.
Should that not work now?

[github-actions]

Searching for maintainers:

• /asus/bios/:model: Route not found

To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.

If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
如果所有路由都无法匹配，issue 将会被自动关闭。如果 issue 和路由无关，请使用 NOROUTE 关键词，或者留下评论。我们会重新审核。

[b9AcE]

Now it works for me.
Thank you!