Troubleshooting¶
gpg¶
Most errors using gpg keys are related either to the gpg key or subkey being expired or the key or subkey is not trusted.
Trust Key¶
gpg --edit-key <key-id>
Secret key is available.
gpg> trust
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
gpg> save
Change Expiry Date¶
Identify the sub key that needs the expiry date changed.
gpg --edit-key <key-id>
gpg> list
sec rsa2048/AF4RGH94ADC84
created: 2019-09-07 expires: 2020-11-15 usage: SC
trust: ultimate validity: ultimate
ssb rsa2048/56ABDJFDKFN
created: 2019-09-07 expired: 2019-09-09 usage: E
[ultimate] (1). Jill Doe (CX) <[email protected]>
Select the sub key (ssb)
gpg> key 1
sec rsa2048/AF4RGH94ADC84
created: 2019-09-07 expires: 2020-11-15 usage: SC
trust: ultimate validity: ultimate
ssb* rsa2048/56ABDJFDKFN
created: 2019-09-07 expired: 2019-09-09 usage: E
[ultimate] (1). Jill Doe (CX) <[email protected]>
gpg> expire
...
Changing expiration time for a subkey.
Please specify how long the key should be valid.
0 = key does not expire
<n> = key expires in n days
<n>w = key expires in n weeks
<n>m = key expires in n months
<n>y = key expires in n years
Key is valid for? (0) 2y
Key expires at Wed 9 Sep 16:20:33 2021 GMT
Is this correct? (y/N) y
gpg> save
rclone¶
Upload a test file.
apprise¶
Send test email.
apprise -vv -t 'my title' -b 'my notification body' 'mailto://email:[email protected]'
Logs¶
Logs can be shown by running the following