chore: record iqon db archive panel check
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
# IQON DB archive panel confirmation attempt
|
||||
|
||||
Purpose: record the Chrome/REG.RU panel attempt to close the `DB archive still needs panel confirmation` gate.
|
||||
|
||||
Created: 2026-05-20
|
||||
Updated: 2026-05-20
|
||||
|
||||
## Result
|
||||
|
||||
Status: `BLOCKED`, not confirmed.
|
||||
|
||||
## Evidence observed
|
||||
|
||||
1. Chrome was opened to the existing ISPmanager panel at `server71.hosting.reg.ru:1500`.
|
||||
2. ISPmanager `Databases` page opened successfully via direct route.
|
||||
3. Database `u0012812_iqon` is visible in the database list.
|
||||
4. ISPmanager route `func=backup2` opened a blank page; no backup/archive list was visible.
|
||||
5. ISPmanager route `form?func=backup2` also showed no backup/archive data.
|
||||
6. REG.RU personal account page opened, but the active account shown in Chrome was `dsu-project`.
|
||||
7. REG.RU `Все услуги` page showed `У вас пока нет доменов и услуг`, so this account cannot confirm IQON hosting backups.
|
||||
8. GUI click automation was unavailable because macOS denied Assistive Access for `System Events`.
|
||||
9. Chrome DOM automation was unavailable because `Allow JavaScript from Apple Events` is disabled.
|
||||
10. Direct ISPmanager API with the FTP credential was rejected as `Invalid username or password`, so browser session cookies could not be reused safely from CLI.
|
||||
|
||||
## Conclusion
|
||||
|
||||
The database itself is confirmed present in ISPmanager, but the backup archive is still not confirmed. Closing this gate requires one of the following:
|
||||
|
||||
1. Switch Chrome/REG.RU to the account that owns the IQON hosting service, then open `Бэкапы` for the hosting service.
|
||||
2. Provide the downloaded DB archive path for verification.
|
||||
3. Temporarily allow GUI automation or Chrome JavaScript from Apple Events so the panel can be navigated programmatically.
|
||||
|
||||
## Safety
|
||||
|
||||
No destructive action was performed. No DB restore or deletion was attempted. No credential values are stored in this report.
|
||||
Reference in New Issue
Block a user