CCU Backup: Self-signed certificates not working since v2.10.3
Black-Thunder opened this issue · comments
Describe the bug
Since v2.10.3 CCU backups will fail when using self-signed certificates. Downgrading to v2.10.2 fixes this issue and the backup is successful again.
Screenshots & Logfiles
Adapter settings:
Log v2.10.3:
Started ccu ...
[DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.2.5/Backups/ioBroker /opt/iobroker/backups"
[DEBUG] [mount] - mount successfully completed
[DEBUG] [mount] - done
[DEBUG] [ccu] - CCU-Backup started ...
[ERROR] [ccu] - self-signed certificate
backitup.0 | 2024-01-21 12:17:15.552 | error | [ccu] self-signed certificate
backitup.0 | 2024-01-21 12:17:15.551 | error | [ccu/ccu] self-signed certificate
backitup.0 | 2024-01-21 12:17:15.430 | debug | [ccu/ccu] CCU-Backup started ...
backitup.0 | 2024-01-21 12:17:13.622 | debug | [ccu/mount] done
backitup.0 | 2024-01-21 12:17:13.620 | debug | [ccu/mount] mount successfully completed
backitup.0 | 2024-01-21 12:17:13.424 | debug | [ccu/mount] cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.2.5/Backups/ioBroker /opt/iobroker/backups"
backitup.0 | 2024-01-21 12:17:03.421 | debug | Backup has started ...
backitup.0 | 2024-01-21 12:17:03.326 | debug | The local storage check was completed successfully. On the host "raspberrypi-gang" are currently 923032 MB free space available!
backitup.0 | 2024-01-21 12:17:01.785 | debug | The local storage check was completed successfully. On the host "raspberrypi-gang" are currently 923032 MB free space available!
Log v2.10.2:
Started ccu ...
[DEBUG] [mount] - cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.2.5/Backups/ioBroker /opt/iobroker/backups"
[DEBUG] [mount] - mount successfully completed
[DEBUG] [mount] - done
[DEBUG] [ccu] - CCU-Backup started ...
[DEBUG] [ccu] - CCU Version: 3.73.9.20231130
[DEBUG] [ccu] - Requesting backup from CCU
[DEBUG] [ccu] - CCU-Backup for is finish
[DEBUG] [ccu] - done
[DEBUG] [cifs] - used copy path: /Backups/ioBroker
[DEBUG] [cifs] - done
[DEBUG] [clean] - No older backup files are deleted, because this backup was started manually
[DEBUG] [clean] - done
[DEBUG] [pushover] - done
[DEBUG] [historyHTML] - new history html values created
[DEBUG] [historyHTML] - done
[DEBUG] [historyJSON] - new history json values created
[DEBUG] [historyJSON] - done
[DEBUG] [umount] - mount activ, umount is started ...
[DEBUG] [umount] - umount successfully completed
[DEBUG] [umount] - done
[EXIT] 0
Versions:
- Adapter version: 2.10.3
- JS-Controller version: 5.0.17
- Node version: v18.19.0
- Operating system: Raspberry Pi OS (64-bit) Bullseye
Please test v2.10.4
Sadly still not working:
2024-01-21 23:40:35.948 - info: backitup.0 (699439) starting. Version 2.10.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-01-21 23:40:36.009 - silly: backitup.0 (699439) States system redis pmessage io.system.adapter.backitup.0.logLevel/io.system.adapter.backitup.0.logLevel:{"val":"silly","ack":true,"ts":1705876835985,"q":0,"from":"system.adapter.backitup.0","lc":1705876821547}
2024-01-21 23:40:36.015 - debug: backitup.0 (699439) Backitup has recognized a linux system
2024-01-21 23:40:36.047 - info: backitup.0 (699439) [iobroker] backup will be activated at 23:05 every 1 day(s)
2024-01-21 23:40:36.146 - info: backitup.0 (699439) [ccu] backup will be activated at 02:45 every 1 day(s)
2024-01-21 23:40:36.192 - debug: backitup.0 (699439) cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.2.5Backups/ioBroker /opt/iobroker/backups"
2024-01-21 23:40:36.961 - silly: backitup.0 (699439) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.backitup.0.eventLoopLag
2024-01-21 23:40:36.964 - debug: backitup.0 (699439) first mount attempt with smb option failed. try next mount attempt without smb option ...
2024-01-21 23:40:36.964 - debug: backitup.0 (699439) cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.5Backups/ioBroker /opt/iobroker/backups"
2024-01-21 23:40:37.198 - debug: backitup.0 (699439) mount successfully completed
2024-01-21 23:40:39.210 - debug: backitup.0 (699439) detect backup file 1 from NAS: iobroker_2024_01_17-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:39.211 - debug: backitup.0 (699439) detect backup file 2 from NAS: iobroker_2024_01_18-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:39.212 - debug: backitup.0 (699439) detect backup file 3 from NAS: iobroker_2024_01_19-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:39.212 - debug: backitup.0 (699439) detect backup file 4 from NAS: iobroker_2024_01_20-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:39.213 - debug: backitup.0 (699439) detect backup file 5 from NAS: iobroker_2024_01_21-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:39.214 - debug: backitup.0 (699439) detect last backup file: iobroker_2024_01_21-23_05_20_backupiobroker.tar.gz
2024-01-21 23:40:44.308 - silly: backitup.0 (699439) States user redis pmessage io.backitup.0.oneClick.*/io.backitup.0.oneClick.ccu:{"val":true,"ack":false,"ts":1705876844306,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1705876844306}
2024-01-21 23:40:44.318 - debug: backitup.0 (699439) The local storage check was completed successfully. On the host "raspberrypi-gang" are currently 923028 MB free space available!
2024-01-21 23:40:44.386 - debug: backitup.0 (699439) Backup has started ...
2024-01-21 23:40:44.395 - debug: backitup.0 (699439) [ccu/mount] mount activ... umount is started before mount!!
2024-01-21 23:40:44.445 - debug: backitup.0 (699439) [ccu/mount] umount successfully completed
2024-01-21 23:40:54.386 - debug: backitup.0 (699439) [ccu/mount] cifs-mount command: "sudo mount -t cifs -o username=iobroker_backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.2.5/Backups/ioBroker /opt/iobroker/backups"
2024-01-21 23:40:54.544 - debug: backitup.0 (699439) [ccu/mount] mount successfully completed
2024-01-21 23:40:54.546 - debug: backitup.0 (699439) [ccu/mount] done
2024-01-21 23:40:56.356 - debug: backitup.0 (699439) [ccu/ccu] CCU-Backup started ...
2024-01-21 23:40:56.466 - error: backitup.0 (699439) [ccu/ccu] self-signed certificate
2024-01-21 23:40:56.467 - error: backitup.0 (699439) [ccu] self-signed certificate
Did you upload via Github after the update?
Yes, I've installed the latest version from GitHub und uploaded the changes. Also just checked that the changes you made to "40-ccu.js" are present on my system. Still same error/issue.
The switch to Axios caused some difficulties with the self-signed certificates.
Should now work again in v2.10.5. I have just recreated all variants
Yes, with v2.10.5 CCU backups work without issues again. Thanks for the quick fix 👍