Skip to content

Disable custom front-end on new firmware #1839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mutatrum wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Disable custom front-end on new firmware #1839

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions main/http_server/http_server.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1805,6 +1805,9 @@ esp_err_t POST_OTA_update(httpd_req_t * req)

snprintf(GLOBAL_STATE->SYSTEM_MODULE.firmware_update_status, 20, "Rebooting...");

// Reset custom WWW so the newly flashed firmware uses its matching embedded Web UI by default
nvs_config_set_bool(NVS_CONFIG_USE_CUSTOM_WWW, false);

httpd_resp_set_type(req, "text/plain");
httpd_resp_sendstr(req, "Firmware update complete, rebooting now!\n");
ESP_LOGI(TAG, "Restarting System because of Firmware update complete");
Expand Down
14 changes: 14 additions & 0 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,20 @@ Starting with the unified firmware releases, ESP-Miner uses a unified architectu

A separate Web UI image (`www.bin`) is no longer required for standard usage since the web interface is served directly from the firmware. If you want to use a custom or modified AxeOS frontend, you can still enable the **custom web UI** option in the settings. This allows you to upload and serve a separate `www.bin` from the SPIFFS partition, which takes priority over the built-in assets.

### Disabling Custom Web UI via API

If a device is stuck serving an older custom `www.bin` partition and the Web UI settings option is not accessible, you can disable `useCustomWWW` directly via the REST API:

```bash
# Disable custom Web UI (revert to embedded AxeOS)
curl -X PATCH http://YOUR-BITAXE-IP/api/system \
-H "Content-Type: application/json" \
-d '{"useCustomWWW": 0}'

# Restart the device to apply changes
curl -X POST http://YOUR-BITAXE-IP/api/system/restart
```

### Rollback to Pre-Unified Firmware

If you roll back the firmware from a unified version to an older, pre-unified version (which expects a separate web partition):
Expand Down
Loading