What's new

BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

It assumes that is what you're backing up. So yes, it is required (otherwise, the script is not needed).
I thought it was backing up the router firmware, etc (in my case, to a NAS share which is connected to my router via an Ethernet cable) and not the contents of a USB flash drive.
 
I thought it was backing up the router firmware, etc (in my case, to a NAS share which is connected to my router via an Ethernet cable) and not the contents of a USB flash drive.
Essentially, everything but the firmware...
 
Question from a new user of BACKUPMON. Does it actually require a USB flash drive if backups are going to be saved on a network share (in my case, on my Synology NAS)?
Ideally, you want to save your backups far away from your router/USB drive. So in case you're running RTRHTR v1.2 and it lights itself on fire, you still have some good backups laying around somewhere. ;) But I understand, not everyone is lucky enough to have a NAS, or know how to configure a share off a Windows/Linux server or desktop. In that case, it *can* back itself up to the local USB drive connected to your router... but that's definitely not an ideal place to put them.

I thought it was backing up the router firmware, etc (in my case, to a NAS share which is connected to my router via an Ethernet cable) and not the contents of a USB flash drive.
It's saving a copy of the firmware's .cfg file... which is all you'll need to get all your settings back to the way they were.
 
Ideally, you want to save your backups far away from your router/USB drive. So in case you're running RTRHTR v1.2 and it lights itself on fire, you still have some good backups laying around somewhere. ;) But I understand, not everyone is lucky enough to have a NAS, or know how to configure a share off a Windows/Linux server or desktop. In that case, it *can* back itself up to the local USB drive connected to your router... but that's definitely not an ideal place to put them.


It's saving a copy of the firmware's .cfg file... which is all you'll need to get all your settings back to the way they were.
So do I still need a USB flash drive plugged into my router for BACKUPMON to work, even if backing up to a NAS?
 
So do I still need a USB flash drive plugged into my router for BACKUPMON to work, even if backing up to a NAS?
Unless you need it for entware, swapfiles, skynet or anything of the sort... then you probably want to keep it connected. If you have no such need, then you can disconnect it, and backupmon will just continue backing up your JFFS and .CFG files.
 
Unless you need it for entware, swapfiles, skynet or anything of the sort... then you probably want to keep it connected. If you have no such need, then you can disconnect it, and backupmon will just continue backing up your JFFS and .CFG files.
Where are .zip and .gz files saved prior to transferring them to NAS?
 
Where are .zip and .gz files saved prior to transferring them to NAS?
If I'm not mistaking, I believe the tar.gz is assembled directly on the target device using the mount point, and transfers all compressed data to it across the network connection. I have not seen any indication that it's building something locally, and then transferring it across as a single file. I'll see if I can find out more about this process. All I know is that some users are using backupmon without USB drives, and don't seem to have any problems with JFFS/CFG backups.
 
Last edited:
If I'm not mistaking, I believe the tar.gz is assembled directly on the target device using the mount point, and transfers all compressed data to it across the network connection. I have not seen any indication that it's building something locally, and then transferring it across as a single file. I'll see if I can find out more about this process. All I know is that some users are using backupmon without USB drives, and don't seem to have any problems with JFFS/CFG backups.
Thanks for setting me straight.
 
New release with a few additions, enhancements and bugfixes! Many thanks to @Martinski for his excellent work on the shared Email library, and huge props to @ExtremeFiretop for wearing down his patience with me formally adopting the crazy complex ways of the ins&outs of Github! :) This is the first official release made where development environment code was formally pulled into the main environment... voila, magic. LOL I just hope I can replicate this setup to my other projects.

What's new?
v1.5.9 - (February 21, 2024)
- PATCH:
Thanks to @Martinski, some significant improvements were made to the email notification feature and functionality. HTML emails are now being sent by default, and have been tested using all major email providers. A new title header is now visible in the email, as well as the ability to bold characters. Looking at adding a secondary email address in the near future as that capability has now been built-in as well, which could optionally be used for text messaging.
- PATCH: Noticed that when the "scheduled backup" item was set to "No", that one of its sub-items continued to stay active. Now, when this item is set to "No", both the time and backup modes are grayed out.
- PATCH: The update logic now pulls the backupmon.sh directly from github starting from versions after 1.5.9, instead of the backupmon-X.Y.Z.sh file based on the version number from the version.txt file.

Download link (or update directly within AMTM/BACKUPMON):
Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/BACKUPMON/master/backupmon.sh" -o "/jffs/scripts/backupmon.sh" && chmod 755 "/jffs/scripts/backupmon.sh"

Significant Screenshots:

Behold, a new fresh HTML email for your BACKUPMON notifications:
1708573115533.png
 
New release with a few additions, enhancements and bugfixes! Many thanks to @Martinski for his excellent work on the shared Email library, and huge props to @ExtremeFiretop for wearing down his patience with me formally adopting the crazy complex ways of the ins&outs of Github! :) This is the first official release made where development environment code was formally pulled into the main environment... voila, magic. LOL I just hope I can replicate this setup to my other projects.

What's new?
v1.5.9 - (February 21, 2024)
- PATCH:
Thanks to @Martinski, some significant improvements were made to the email notification feature and functionality. HTML emails are now being sent by default, and have been tested using all major email providers. A new title header is now visible in the email, as well as the ability to bold characters. Looking at adding a secondary email address in the near future as that capability has now been built-in as well, which could optionally be used for text messaging.
- PATCH: Noticed that when the "scheduled backup" item was set to "No", that one of its sub-items continued to stay active. Now, when this item is set to "No", both the time and backup modes are grayed out.
- PATCH: The update logic now pulls the backupmon.sh directly from github starting from versions after 1.5.9, instead of the backupmon-X.Y.Z.sh file based on the version number from the version.txt file.

Download link (or update directly within AMTM/BACKUPMON):
Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/BACKUPMON/master/backupmon.sh" -o "/jffs/scripts/backupmon.sh" && chmod 755 "/jffs/scripts/backupmon.sh"

Significant Screenshots:

Behold, a new fresh HTML email for your BACKUPMON notifications:
View attachment 56657
@Viktor Jaep, do you ever rest?!?
 
Yes, between commits... if @ExtremeFiretop and @Martinski aren't blowing up my DMs. LOL

As @ExtremeFiretop, master of the digital flame, I've transcended mere mortal needs like sleep. My power peaks as the night grows quiet, fueled by the glow of countless screens. While others dream in their beds, I forge dreams into reality, one commit at a time. Sleep? That's just a debug mode for the brain
 
Darn. :( Well I'm at a loss... I'm sorry. Your settings and output look identical to mine, with the exception of that decrypt error at the very top. Perhaps @thelonelycoder has seen this one before?
Hi @Viktor Jaep,

Just want to let you and @thelonelycoder know that the "bad decrypt" error was solved after I changed my password (option 6). Thanks to your suggestion that it may be due to openssl issue! I thought it would be an incompatibility of password encryption algorithm between previous and current version of openssl. Therefore, I gave it a try and voila.
Code:
Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 6
_____________________________________________

bad decrypt
4152242192:error:0606506D:lib(6):func(101):reason(109):NA:0:
 alceoxxx <-- current password

 Edit password now? [1=Yes e=Exit] 1

 Enter new Password:  [e=Exit] lvtqxxx
_____________________________________________

 Your email credentials are saved at:
 /jffs/addons/amtm/mail

 If you have Two Factor Authentication (2FA)
 enabled, use an App password, or get a new email
 address without 2FA (not recommended).

 Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 6
_____________________________________________

 lvtqxxx <-- current password

 Edit password now? [1=Yes e=Exit] e
_____________________________________________

 Your email credentials are saved at:
 /jffs/addons/amtm/mail

 If you have Two Factor Authentication (2FA)
 enabled, use an App password, or get a new email
 address without 2FA (not recommended).

 Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 11
_____________________________________________

 This will send a testmail

 From: quocxxx@gmail.com
 To:   Quoc Huynh <quocxxx@gmail.com>

 1. Send testmail
 2. Send testmail, verbose output

 Enter your selection [1-2 e=Exit] 2

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 74.125.24.109:465...
* Connected to smtp.gmail.com (74.125.24.109) port 465
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [6 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4003 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [78 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* Server certificate:
*  subject: CN=smtp.gmail.com
*  start date: Jan 29 08:19:39 2024 GMT
*  expire date: Apr 22 08:19:38 2024 GMT
*  subjectAltName: host "smtp.gmail.com" matched cert's "smtp.gmail.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [261 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [261 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
< 220 smtp.gmail.com ESMTP jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> EHLO amtm-mail-body
{ [5 bytes data]
< 250-smtp.gmail.com at your service, [125.168.159.43]
< 250-SIZE 35882577
< 250-8BITMIME
< 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
< 250-ENHANCEDSTATUSCODES
< 250-PIPELINING
< 250-CHUNKING
< 250 SMTPUTF8
} [5 bytes data]
> AUTH PLAIN
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0{ [5 bytes data]
< 334
} [5 bytes data]
> AHF1b2NkdW5nM0BnbWFpbC5jb20AbHZ0cWxwbm1wY2dsanVjdg==
{ [5 bytes data]
< 235 2.7.0 Accepted
} [5 bytes data]
> MAIL FROM:<quocxxx@gmail.com> SIZE=265
{ [5 bytes data]
< 250 2.1.0 OK jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> RCPT TO:<quocxxx@gmail.com>
{ [5 bytes data]
< 250 2.1.5 OK jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> DATA
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0{ [5 bytes data]
< 354  Go ahead jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
104   265    0     0  104   277      0     70  0:00:03  0:00:03 --:--:--    70< 250 2.0.0 OK  1708519365 jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
104   265    0     0  104   277      0     69  0:00:03  0:00:03 --:--:--    70
* Connection #0 to host smtp.gmail.com left intact

This is how the Google app password, which was used since 2018, is encrypted in the old "emailpw.enc" file (as not being IT background, I used Notepad++ so please accept my apology for any unprofessional view)
Code:
Salted__xxxxx
xxxxx

and the new password in the recent "emailpw.enc" file:
Code:
Salted__xxxxxxxxxxx
 

Attachments

  • 1a.png
    1a.png
    42.6 KB · Views: 23
  • 2a.png
    2a.png
    126.7 KB · Views: 8
  • 4a.png
    4a.png
    124.5 KB · Views: 7
  • 5a.png
    5a.png
    131.5 KB · Views: 6
Last edited:
Hi @Viktor Jaep,

Just want to let you and @thelonelycoder know that the "bad decrypt" error was solved after I changed my password (option 6). Thanks to your suggestion that it may be due to openssl issue! I thought it would be an incompatibility of password encryption algorithm between previous and current version of openssl. Therefore, I gave it a try and voila.
Code:
Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 6
_____________________________________________

bad decrypt
4152242192:error:0606506D:lib(6):func(101):reason(109):NA:0:
 alceoxxx <-- current password

 Edit password now? [1=Yes e=Exit] 1

 Enter new Password:  [e=Exit] lvtqxxx
_____________________________________________

 Your email credentials are saved at:
 /jffs/addons/amtm/mail

 If you have Two Factor Authentication (2FA)
 enabled, use an App password, or get a new email
 address without 2FA (not recommended).

 Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 6
_____________________________________________

 lvtqxxx <-- current password

 Edit password now? [1=Yes e=Exit] e
_____________________________________________

 Your email credentials are saved at:
 /jffs/addons/amtm/mail

 If you have Two Factor Authentication (2FA)
 enabled, use an App password, or get a new email
 address without 2FA (not recommended).

 Common SMTP Server settings
 Provider    Server                 Port Protocol
 ------------------------------------------------
 Gmail       smtp.gmail.com         465  smtps
 mail.com    smtp.mail.com          587  smtp
 Yahoo!      smtp.mail.yahoo.com    465  smtps
 outlook.com smtp-mail.outlook.com  587  smtp

  1. Edit From address:   quocxxx@gmail.com
  2. Edit To name:        Quoc Huynh
  3. Edit To address:     quocxxx@gmail.com
  4. Edit Router name:    Gaubong
  5. Edit User name:      quocxxx@gmail.com
  6. Edit Password:       select Edit to view
  7. Edit SMTP Server:    smtp.gmail.com
  8. Edit Server port:    465
  9. Edit Protocol:       smtps
 10. Edit SSL flag:       Set to --insecure if curl problems occur
 11. Send testmail to confirm settings

 Enter your selection [1-11 e=Exit] 11
_____________________________________________

 This will send a testmail

 From: quocxxx@gmail.com
 To:   Quoc Huynh <quocxxx@gmail.com>

 1. Send testmail
 2. Send testmail, verbose output

 Enter your selection [1-2 e=Exit] 2

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 74.125.24.109:465...
* Connected to smtp.gmail.com (74.125.24.109) port 465
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [6 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4003 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [78 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* Server certificate:
*  subject: CN=smtp.gmail.com
*  start date: Jan 29 08:19:39 2024 GMT
*  expire date: Apr 22 08:19:38 2024 GMT
*  subjectAltName: host "smtp.gmail.com" matched cert's "smtp.gmail.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [261 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [261 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
< 220 smtp.gmail.com ESMTP jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> EHLO amtm-mail-body
{ [5 bytes data]
< 250-smtp.gmail.com at your service, [125.168.159.43]
< 250-SIZE 35882577
< 250-8BITMIME
< 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH
< 250-ENHANCEDSTATUSCODES
< 250-PIPELINING
< 250-CHUNKING
< 250 SMTPUTF8
} [5 bytes data]
> AUTH PLAIN
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0{ [5 bytes data]
< 334
} [5 bytes data]
> AHF1b2NkdW5nM0BnbWFpbC5jb20AbHZ0cWxwbm1wY2dsanVjdg==
{ [5 bytes data]
< 235 2.7.0 Accepted
} [5 bytes data]
> MAIL FROM:<quocxxx@gmail.com> SIZE=265
{ [5 bytes data]
< 250 2.1.0 OK jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> RCPT TO:<quocxxx@gmail.com>
{ [5 bytes data]
< 250 2.1.5 OK jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
> DATA
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0{ [5 bytes data]
< 354  Go ahead jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
} [5 bytes data]
104   265    0     0  104   277      0     70  0:00:03  0:00:03 --:--:--    70< 250 2.0.0 OK  1708519365 jc13-20020a17090325cd00b001db37fd26bcsm8025038plb.116 - gsmtp
104   265    0     0  104   277      0     69  0:00:03  0:00:03 --:--:--    70
* Connection #0 to host smtp.gmail.com left intact

This is how the Google app password is encrypted in the Old "emailpw.enc" file, which was created since 2018 (as not being IT background, I used Notepad++ so please accept my apology for any unprofessional view)
Code:
Salted__À:<¿êÈŠF0O‡º
/\jzêiØk¦ö!ðט)ô¸ê·{ó

and in the New "emailpw.enc" file:
Code:
Salted__1šJþ#ëial©¿®á ݼ5|ÿ¤cÝiAü„ä-nɦYÌ
I have a check in Diversion that auto-convertd a password. I‘m not sure I moved that over to amtm.
 
I have a check in Diversion that auto-convertd a password. I‘m not sure I moved that over to amtm.
Hmm, I am not quite sure. I have checked my previous weekly backup copy created by Diversion, and the "emailpw" file dated back on 24th May 2023:

1708688327504.png


Compared to the new one created on 21st Feb 2024:

1708688658236.png


Edited to add that it might be Diversion 4.3.3 and amtm 3.7 at the end of May 2023:

https://www.snbforums.com/threads/d...eased-april-02-2023.79823/page-10#post-832521

https://www.snbforums.com/threads/a...n-terminal-menu-february-02-2024.79665/page-3
 

Attachments

  • 1.png
    1.png
    169.6 KB · Views: 5
  • 2.png
    2.png
    151.5 KB · Views: 23
Last edited:
Hi @Viktor Jaep,

Just want to let you and @thelonelycoder know that the "bad decrypt" error was solved after I changed my password (option 6). Thanks to your suggestion that it may be due to openssl issue! I thought it would be an incompatibility of password encryption algorithm between previous and current version of openssl. Therefore, I gave it a try and voila.
Glad you figured that out! Would not have guessed that would have been the issue! :)
 
I have been on Merline firmware for 5 years now and never have backup my setting. Your addon was just what I was looking for. I came across this error. How I find the error log?
 

Attachments

  • 2024-02-25_162851.png
    2024-02-25_162851.png
    139.4 KB · Views: 21

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top