Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies
fix(api): stop blocking user mutations on Mihomo reload; raise mutation timeouts
Root cause: create/delete users (and node ops) waited on ApplyConfig (mihomo -t +
restart), often exceeding the 30s axios timeout and surfacing as
"Cannot reach the panel API" even when the DB write succeeded.
- Debounced async credentials→config reload after user changes
- Axios: 45s default, 120s for non-GET mutations
- Clearer network error hint; listener RegenerateConfig generates under lock then applies