Description of the bug or feature request

Environment

bettercap v2.32.0 (built for linux arm with go1.15.15)
Linux raspberry-pi 5.10.92-v7+ armv7l GNU/Linux
Raspbian GNU/Linux 11 (bullseye)

cli:
/usr/local/bin/bettercap -no-colors -eval "set events.stream.output /var/log/bettercap.log" -caplet undermuz-basic

cat /usr/local/share/bettercap/caplets/undermuz-basic.cap

# api listening on https://0.0.0.0:8083/ and ui on https://0.0.0.0
set api.rest.address 0.0.0.0
set api.rest.port 8083
set https.server.address 0.0.0.0
set https.server.port 443

# make sure both use the same https certificate so api requests won't fail
set https.server.certificate ~/.bettercap-https.cert.pem
set https.server.key ~/.bettercap-https.key.pem 
set api.rest.certificate ~/.bettercap-https.cert.pem
set api.rest.key ~/.bettercap-https.key.pem 
# default installation path of the ui
set https.server.path /usr/local/share/bettercap/ui

set api.rest.username <user>
set api.rest.password <pass>

api.rest on
https.server on

#WIFI
set wifi.interface wlan1
set wifi.handshakes.file ~/hs
set wifi.handshakes.aggregate false
wifi.recon on

Steps to Reproduce

1. deauth several ap
2. got some handshakes
3. try convert any of handshakes by https://hashcat.net/cap2hashcat/index.pl
4. OR try upload to onlinehashcrack: curl -X POST -F "email=SOME_VALID_EMAIL" -F "file=@/path/to/handshake.pcap" https://api.onlinehashcrack.com
5. got error No valid EAPOL handshake or PMKID found

Expected behavior: Expected to had a valid handshake

Actual behavior: Not getting valid handshakes

--

BTW, when wifi.handshakes.aggregate true, an aggregated file with handshakes is valid, and can be uploaded to onlinehashcrack