Wrong Repo Link for Pi.Alert LXC

[leiweibau]

Hello,
just found out that my fork has been honored to be included in your list. Unfortunately, the link on your homepage points to the main project. I would be happy if this is updated as well. Of course I am available for any questions myself.

Knowing this list, however, also shows me that I need to change a small part of the software, as it can produce an error when used outside of a user folder under very specific circumstances. I will address this in a timely manner.

[tteck]

Apologies for the link error; it has been rectified.

[tteck]

It would be highly beneficial if you could develop an update script within your install directory for managing the LXC installation paths. If this task is too time-consuming or isn't aligned with your interests, I will create one for this repository.

[leiweibau]

Since I don't have the software infrastructure in my home lab to build or test LXC containers, it would be more productive if you would do that.

At this point I would like to inform you about the mentioned "bug" in connection with the installation outside the home directory.
This is currently in the pialert-cli. To determine the user under which Pi.Alert was installed, I determine the parent directory. "whoami" did not help me when I need to run the pialert-cli with "sudo". Specifically, I can think of just one function that affects this, but which I could rewrite. Since I'm on the road right now, I can't look any further. But I will evaluate the code again from the point of view of the LXC installation.

[tteck]

Edit: LXC containers run as the root user unless the user explicitly creates another user within the container.

I haven't encountered any issues with the "pialert-cli", and all the commands I've tried, such as /opt/pialert/back/pialert-cli disable_scan 1, have worked as expected.

Concerning the update script, if you would consider replacing INSTALL_DIR=~ with

echo -e "LXC users should specify '/opt' or simply press Enter if no customization is needed."
read -p "Enter the installation directory: " INSTALL_DIR
[ -z "$INSTALL_DIR" ] && INSTALL_DIR=~

in your update script that would cover the LXC installation as well as preserve your installation. Just a thought.

[leiweibau]

Its "pialert-cli set_permissions"
The "1" is not necessary

[leiweibau]

echo -e "LXC users should specify '/opt' or simply press Enter if no customization is needed."
read -p "Enter the installation directory: " INSTALL_DIR
[ -z "$INSTALL_DIR" ] && INSTALL_DIR=~

I will take a look

[tteck]

Its "pialert-cli set_permissions"

Indeed, I understand now.

[leiweibau]

I will change this to "chgrp"

[leiweibau]

For information for future integration
leiweibau/Pi.Alert@5004863

[leiweibau]

I will add an option to the updatescript, as I did in the pialert-cli, hoping that it will then work in the LXC container.

[tteck]

What are your thoughts on using "git clone" and subsequent updates using "git pull"?

[leiweibau]

git is a big mystery to me. I use it forced to maintain the fork, but otherwise have little experience with it.

[tteck]

When you install using "git clone," your installation reflects the state of the main branch at the time of the install. Subsequently, using "git pull" will update your installation with any new commits, making the creation of a .tar file unnecessary for this type of installation.

A typical update preserving the "config" and "db" directories would be:

cd /opt/pialert
cp -R config config-backup
cp -R db db-backup
git pull
cp -R config-backup/* config
cp -R db-backup/* db
rm -rf config-backup db-backup

In most cases, you won't need to reset file permissions after a "git pull" unless new files are added in the updated codebase. Git itself does not typically modify file permissions during regular pull operations.

I'm thinking about switching I switched to this install method in this repository with the aim of making the process more streamlined and simplified.

Excluding dependencies, the installation process for Pi.Alert would be:

git clone -q https://github.com/leiweibau/Pi.Alert.git /opt/pialert
mkdir -p /opt/pialert/front/reports
rm -rf /var/www/html/index.html /opt/pialert/{docs,install,tar}
mv /var/www/html/index.lighttpd.html /var/www/html/index.lighttpd.html.old
ln -s /opt/pialert/install/index.html /var/www/html/index.html
ln -s /opt/pialert/front /var/www/html/pialert
chmod go+x /opt/pialert /opt/pialert/back/shoutrrr/x86/shoutrrr
chgrp -R www-data /opt/pialert/db /opt/pialert/front/reports /opt/pialert/config /opt/pialert/config/pialert.conf
chmod -R 775 /opt/pialert/db /opt/pialert/db/temp /opt/pialert/config /opt/pialert/front/reports
touch /opt/pialert/log/pialert.vendors.log /opt/pialert/log/pialert.IP.log /opt/pialert/log/pialert.1.log /opt/pialert/log/pialert.cleanup.log /opt/pialert/log/pialert.webservices.log
src_dir="/opt/pialert/log"
dest_dir="/opt/pialert/front/php/server"
for file in pialert.vendors.log pialert.IP.log pialert.1.log pialert.cleanup.log pialert.webservices.log; do
    ln -s "$src_dir/$file" "$dest_dir/$file"
done
sed -i 's#PIALERT_PATH\s*=\s*'\''/home/pi/pialert'\''#PIALERT_PATH           = '\''/opt/pialert'\''#' /opt/pialert/config/pialert.conf

[leiweibau]

Sounds interesting. I'll keep that in mind for the future, but won't change it for now, since I only work with one branch and thus all my pulls would be "activated" immediately. I admit, however, that the creation of the tar file, the compilation of the innovations, changes and fixes still offers some potential for optimization 😉

[tteck]

To give you an idea of what the Proxmox Pi.Alert installation looks like.

    ____  _   ___    __          __
   / __ \(_) /   |  / /__  _____/ /_
  / /_/ / / / /| | / / _ \/ ___/ __/
 / ____/ / / ___ |/ /  __/ /  / /_
/_/   /_(_)_/  |_/_/\___/_/   \__/

Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Container ID: 112
Using Hostname: pialert
Using Disk Size: 3
Allocated Cores: 1
Allocated RAM: 512
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Disable IPv6: yes
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a PiAlert LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using local-lvm for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 112 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.86.253 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.113.3
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Installed PHP Dependencies
 ✓ Installed Python Dependencies
 ✓ Installed Pi.Alert
 ✓ Finished Pi.Alert Scan
 ✓ Customized Container
 ✓ Cleaned
 ✓ Completed Successfully!

PiAlert should be reachable by going to the following URL.
         http://192.168.86.253/pialert/ 

[leiweibau]

I see you are using Debian 12, I was a bit worried at the beginning because of the handling of external sources with Python3. But fortunately it is still possible to install them.
I've been thinking about installing a proxmox server for a while, but haven't been able to bring myself to do it yet.

[tteck]

Yeah, I handle Debian 12 a little differently, I'll put in a PR so that one install script will handle all

[tteck]

Proxmox/misc/install.func

Line 86 in 5a52609

rm -rf /usr/lib/python3.*/EXTERNALLY-MANAGED

I use it in all installations within this repository.

[nallak]

HI Tteck

I like the work you made with all your script , got a good bunch installed up and running for my HomeLAB
Recently i installed Pi-Alert which works flawlessly ( inc Pushsafer notifyer).

I'm new to this and wanted to try to change the default password 1***** , i tried via CLI within proxmox with my logins
but somehow i can't access the required location.
I'm pretty sure im doing something worng :D
Can you explain where to start to run " To change password run: ./pialert-cli set_password new_password
in the "~/pialert/back" folder."

Thanks in advanced

[tteck]

Well, first it's /opt/pialert/back

[tteck]

With the LXC install, always replace ~ with /opt

[nallak]

Thans for the feedback i wil try this out !

[leiweibau]

I'll see if I can change the script to give the correct path depending on the install environment.

[nallak]

@leiweibau
Sounds like a plan ...

also you Thanks for these scripts, makes life eazyer .

[tteck]

@leiweibau In your latest release, I've noticed that in the update_vendors.sh file, you're using the cp command (sudo cp -n /usr/share/ieee-data/*.* /var/lib/ieee-data) every time the script is called. Have you considered using a symbolic link instead? You could add a line to create the symlink in the install.sh script, like this: ln -s /usr/share/ieee-data/ /var/lib/. This approach might be a better choice for managing the data, and it eliminates the need to create the /var/lib/ieee-data directory.

I've already incorporated this method in this repository, and it has worked well. Additionally, it's worth considering whether it's necessary to create backups of these files that can easily be recreated.

Speaking of creating those files with:

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/iab/iab.csv"
sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/iab/iab.txt"

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui28/mam.csv"
sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui28/mam.txt"

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui36/oui36.csv"
sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui36/oui36.txt"

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui/oui.csv"
sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true "https://standards-oui.ieee.org/oui/oui.txt"

This single command accomplishes the same as your multiple commands but is more concise and easier to manage.

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true \
  "https://standards-oui.ieee.org/oui/oui.csv" \
  "https://standards-oui.ieee.org/oui/oui.txt" \
  "https://standards-oui.ieee.org/oui36/oui36.csv" \
  "https://standards-oui.ieee.org/oui36/oui36.txt" \
  "https://standards-oui.ieee.org/oui28/mam.csv" \
  "https://standards-oui.ieee.org/oui28/mam.txt"

Just tossing around ideas

[leiweibau]

Yes, you are right. I first encountered this problem under DietPi and used the copy command because get-oui ran into an error (Both "ieee-data" folders did not exist). Then on the other operating systems I found that symlinks were being used. However, since the installation script ran cleanly, I left it at that for now. I'll probably replace the cp command with a symlink because it just makes more sense, I just didn't have time this morning to test 6 installations again 😉.

I have also thought about the necessity of the backup in both folders. I will probably remove this as well.

This single command accomplishes the same as your multiple commands but is more concise and easier to manage.

Good point, I hadn't thought of that.

[leiweibau]

sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true
"https://standards-oui.ieee.org/oui/oui.csv"
"https://standards-oui.ieee.org/oui/oui.txt"
"https://standards-oui.ieee.org/oui36/oui36.csv"
"https://standards-oui.ieee.org/oui36/oui36.txt"
"https://standards-oui.ieee.org/oui28/mam.csv"
"https://standards-oui.ieee.org/oui28/mam.txt"

to get this work, i have to use the parameter "-Z"

[tteck]

What happened to the back slashes?

[leiweibau]

they are still there, Github has removed them in the quote

[tteck]

Here is my update_vendors.sh that seems to be working great.
Note: I'm using a symlink instead of cp (ln -s /usr/share/ieee-data/ /var/lib/)

#!/bin/sh
# ------------------------------------------------------------------------------
#  Pi.Alert
#  Open Source Network Guard / WIFI & LAN intrusion detector 
#
#  update_vendors.sh - Back module. IEEE Vendors db update
# ------------------------------------------------------------------------------
#  Puche 2021        [email protected]        GNU GPLv3
# ------------------------------------------------------------------------------

# ----------------------------------------------------------------------
#  Main directories to update:
#    /usr/share/arp-scan
#    /usr/share/ieee-data
#    /var/lib/ieee-data
# ----------------------------------------------------------------------

echo "Updating /usr/share/ieee-data/..."
cd /usr/share/ieee-data/
sudo aria2c --dir=/usr/share/ieee-data --max-connection-per-server=5 --allow-overwrite=true --quiet=true \
  "https://standards-oui.ieee.org/oui/oui.csv" \
  "https://standards-oui.ieee.org/oui/oui.txt" \
  "https://standards-oui.ieee.org/oui36/oui36.csv" \
  "https://standards-oui.ieee.org/oui36/oui36.txt" \
  "https://standards-oui.ieee.org/oui28/mam.csv" \
  "https://standards-oui.ieee.org/oui28/mam.txt"

echo ""
echo "Updating /usr/share/arp-scan/..."
cd /usr/share/arp-scan
sudo get-oui -v

[leiweibau]

I am currently also working on it

[tteck]

to get this work, i have to use the parameter "-Z"

Admittingly, I've never used aria2c before, but my understanding is that when you use the "-Z" option with "aria2c", it starts the download in a paused state, and nothing will be downloaded until you manually resume the downloads. The "-Z" option essentially initializes the downloads but keeps them paused.

[leiweibau]

When i used your single aria2c call for all files, only the 1st one ist downloaded on raspbianOS. With the -Z option everything is downloaded. Maybe i should switch back to the aria2 call for every single file.

Have you saw this issue leiweibau/Pi.Alert#174 ?
I added a "sudo apt-get update", maybe it solves the problem.

[tteck]

I'm still a fan of using "curl". On these low power gadgets, you can "throttle" the download down, and one less dependency.

curl -s --limit-rate 2M -O \
  "https://standards-oui.ieee.org/oui/oui.csv" \
  "https://standards-oui.ieee.org/oui/oui.txt" \
  "https://standards-oui.ieee.org/oui36/oui36.csv" \
  "https://standards-oui.ieee.org/oui36/oui36.txt" \
  "https://standards-oui.ieee.org/oui28/mam.csv" \
  "https://standards-oui.ieee.org/oui28/mam.txt"

They didn't mention what OS they are using, but your solution should fix the issue.

[leiweibau]

I have nothing against "curl" in principle. It only hinders my testing extremely when 4 files are displayed with 100% and the 5th file stops at maybe 84.7% and the installation has to be aborted.

[tteck]

Maybe try throttling?

[tteck]

Testing the update went smoothly

############################################################################
# You are planning to update Pi.Alert. Please make sure that no scan takes #
# place during the update to avoid possible database errors afterwards!!!  #
#                                                                          #
# This can be done by pausing the Arp scan via the settings page. However, #
# scans that are already running will not be terminated.                   #
############################################################################


Press enter to continue 

############################################################
 Pi.Alert Update
############################################################
Sat Sep 23 14:12:02 EDT 2023
Logfile: pialert_update_2023-09-23_14-11.log

- Checking Python...
Python 3 is installed on your system
mac-vendor-lookup is already installed
fritzconnection is already installed
Installing routeros_api...
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
routeros_api is now installed
Installing unifi...
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
unifi is now installed
- Stopping Pi.Alert...
No timeout is set. Pi.Alert restarts itself with the next scan after 10min.
arp-scan: no process found

Pi.Alert  (2023-09-22)
---------------------------------------------------------
Current User: root 


Test Reporting...
    Skip mail...
    Skip PUSHSAFER...
    Skip PUSHOVER...
    Skip Telegram...
    Skip NTFY...
    Save report to file...

DONE!!!


Configured Pi.Alert scans are disabled

- Reset permissions...
- Deleting previous Pi.Alert backups...
- Creating new Pi.Alert backup...
...............................................................................
- Cleaning previous version...
- Checking packages...
- Installing missing packages: python3-cryptography
- Downloading update file...
/opt/pialert_latest.tar         100%[=======================================================>]  86.00M  9.81MB/s    in 8.8s    
- Uncompressing tar file
.......................................................................................
- Deleting downloaded tar file...
- Generate autocomplete file...
- Copy autocomplete file...
- Config backup...
- Updating config file...
- Updating DB permissions...
- Installing sqlite3...
- Set Permissions...
- Create Logfile Symlinks...
- Set sudoers...
Pi.Alert User: opt

Frontend sudoer
www-data ALL=(ALL) NOPASSWD: /opt/pialert/back/pialert-cli
www-data ALL=(ALL) NOPASSWD: /usr/bin/df

Backend sudoer
opt ALL=(ALL) NOPASSWD: /opt/pialert/back/pialert-cli
opt ALL=(ALL) NOPASSWD: /usr/sbin/arp-scan
opt ALL=(ALL) NOPASSWD: /usr/bin/nmap
- Patch DB...
################################################################################
# You are planning to update the Pi.Alert DB. Please make sure that no scan    #
# takes place during the update to avoid possible database errors afterwards!  #
#                                                                              #
# This can be done by pausing the Arp scan via the settings page. However,     #
# scans that are already running will not be terminated. (STRG+C to Abort)     #
################################################################################


Press enter to continue 

Update DB /opt/pialert/back/../db/pialert.db

Purge old db backup
rm: cannot remove '/opt/pialert/back/../db/pialert.db.bak': No such file or directory
...Create backup before insert new table
...Insert new table 'Online_History' to DB
...Insert new table 'network_infrastructure' to DB
...Insert new column 'dev_Infrastructure' to table 'Devices' to DB
        Column 'dev_Infrastructure' already exists in the 'Devices' table.
...Insert new column 'dev_Infrastructure_port' to table 'Devices' to DB
        Column 'dev_Infrastructure_port' already exists in the 'Devices' table.
...Insert new column 'net_downstream_devices' to table 'network_infrastructure' to DB
        Column 'net_downstream_devices' already exists in the 'network_infrastructure' table.
...Insert new table 'network_dumb_dev' to DB
...Insert new table 'Services_Events' to DB
...Insert new table 'Services_CurrentScan' to DB
...Insert new table 'Services' to DB
...Insert new column 'mon_Notes' to table 'Services' to DB
        Column 'mon_Notes' already exists in the 'Services' table.
...Insert new table 'pialert_journal' to DB
...Insert new column 'dev_Model' to table 'Devices' to DB
        Column 'dev_Model' already exists in the 'Devices' table.
...Insert new column 'dev_Serialnumber' to table 'Devices' to DB
        Column 'dev_Serialnumber' already exists in the 'Devices' table.
...Insert new column 'dev_ConnectionType' to table 'Devices' to DB
        Column 'dev_ConnectionType' already exists in the 'Devices' table.
...Insert new table 'ICMP_Mon' to DB
...Insert new table 'ICMP_Mon_CurrentScan' to DB
...Insert new table 'ICMP_Mon_Events' to DB
...Insert new column 'mon_ssl_subject' to table 'Services' to DB
        Column 'mon_ssl_subject' already exists in the 'Services' table.
...Insert new column 'mon_ssl_issuer' to table 'Services' to DB
        Column 'mon_ssl_issuer' already exists in the 'Services' table.
...Insert new column 'mon_ssl_valid_from' to table 'Services' to DB
        Column 'mon_ssl_valid_from' already exists in the 'Services' table.
...Insert new column 'mon_ssl_valid_to' to table 'Services' to DB
        Column 'mon_ssl_valid_to' already exists in the 'Services' table.
...Insert new column 'mon_ssl_fc' to table 'Services' to DB
        Column 'mon_ssl_fc' already exists in the 'Services' table.
...Insert new column 'cur_ssl_subject' to table 'Services_CurrentScan' to DB
        Column 'cur_ssl_subject' already exists in the 'Services_CurrentScan' table.
...Insert new column 'cur_ssl_issuer' to table 'Services_CurrentScan' to DB
        Column 'cur_ssl_issuer' already exists in the 'Services_CurrentScan' table.
...Insert new column 'cur_ssl_valid_from' to table 'Services_CurrentScan' to DB
        Column 'cur_ssl_valid_from' already exists in the 'Services_CurrentScan' table.
...Insert new column 'cur_ssl_valid_to' to table 'Services_CurrentScan' to DB
        Column 'cur_ssl_valid_to' already exists in the 'Services_CurrentScan' table.
...Insert new column 'cur_ssl_fc' to table 'Services_CurrentScan' to DB
        Column 'cur_ssl_fc' already exists in the 'Services_CurrentScan' table.
...Insert new column 'moneve_ssl_fc' to table 'Services_Events' to DB
        Column 'moneve_ssl_fc' already exists in the 'Services_Events' table.

Update finished!

- Starting Pi.Alert...

Pi.Alert  (2023-09-22)
---------------------------------------------------------
Current User: root 


Test Reporting...
    Skip mail...
    Skip PUSHSAFER...
    Skip PUSHOVER...
    Skip Telegram...
    Skip NTFY...
    Save report to file...

DONE!!!


Configured Pi.Alert scans are enabled
- Testing Pi.Alert HW vendors database update process...
*** PLEASE WAIT A COUPLE OF MINUTES...

Pi.Alert  (2023-09-22)
---------------------------------------------------------
Current User: root 

Update HW Vendors
    Timestamp: 2023-09-23 14:12:00

Updating vendors DB...

Searching devices vendor
    Devices Ignored:   0
    Vendors Not Found: 0
    Vendors updated:   0

Try build in mac-vendor-lookup update
    Update successful

- Testing Pi.Alert Internet IP Lookup...

Pi.Alert  (2023-09-22)
---------------------------------------------------------
Current User: root 

Check Internet IP
    Timestamp: 2023-09-23 14:12:00

Retrieving Internet IP...
    75.37.14.188 #fake

Retrieving previous IP...
    75.37.14.188 #fake
    No changes to perform

Skipping Dynamic DNS update...

DONE!!!



- Testing Pi.Alert Network scan...
*** PLEASE WAIT A COUPLE OF MINUTES...

Pi.Alert  (2023-09-22)
---------------------------------------------------------
Current User: root 

Scan Devices
    Timestamp: 2023-09-23 14:12:00

Scanning...
    arp-scan Method...
    arp-scan: One interface
    Pi-hole Method...
    DHCP Leases Method...
    Fritzbox Method...

Processing scan results...
    Processing ignore list...
        Delete 0 ignored devices from scan on appearance
    Devices Detected.......: 95
        arp-scan Method....: 93
        Pi-hole Method.....: +0
        Fritzbox Method....: +0
        New Devices........: 0

    Devices in this cycle..: 95
        Down Alerts........: 0
        New Down Alerts....: 0
        New Connections....: 0
        Disconnections.....: 0
        IP Changes.........: 0

Updating DB Info...
    Sessions Events (connect / discconnect) ...
    Creating new devices...
    Updating Devices Info...
        Trying to resolve devices without name............................
        Names updated:   0
    Voiding false (ghost) disconnections...
    Pairing session events (connection / disconnection) ...
    Creating sessions snapshot...
    Skipping repeated notifications...
    Calculate Activity History...

Start ICMP Monitoring...
    Get Host/Domain List...
        List contains 0 entries
    Flush previous ping results...
    Ping Hosts...
    No Hosts(s) to monitor!

Reporting...
    Formating report...
    No changes to report...
    Notifications: 0

Reporting (ICMP Monitoring) ...
    No changes to report...

DONE!!!



------------------------------------------------------------
 Update process finished
------------------------------------------------------------

It installed routeros_api and unifi without issue. I noticed that it also installed python3-cryptography which I've never used before, my install utilizes pip3 install cryptography, which one is correct?

[leiweibau]

Okay. My test machine (not a VM) just ran the update without any problems. Maybe the sudo apt-get update helped a bit. I will watch it for a while.

Apart from that, I would like to say thanks for the support. I have the impression that with your help, the installation and update process runs smoother.

[tteck]

I noticed that the update installed pip3 install python3-cryptography which I've never used before, my installation utilizes pip3 install cryptography.

The officially recognized and widely used package for the Python cryptography library is simply cryptography. This is the package maintained by the Python cryptography community and is the one recommended for most users.

[nallak]

FYI

I've updated Mine without any problems. (Proxmox Script) Pi.Alert LXC from tteck

[tteck]

@leiweibau after your commit leiweibau/Pi.Alert@a65d1b3 there is an issue when updating.

Introducing new features in a future release (Speedtest) may disrupt the current update script, resulting in an error message like this: chmod: cannot access '/opt/pialert/back/speedtest/': No such file or directory.

############################################################################
# You are planning to update Pi.Alert. Please make sure that no scan takes #
# place during the update to avoid possible database errors afterwards!!!  #
#                                                                          #
# This can be done by pausing the Arp scan via the settings page. However, #
# scans that are already running will not be terminated.                   #
############################################################################


Press enter to continue 

############################################################
 Pi.Alert Update
############################################################
Sun Oct  1 06:55:21 EDT 2023
Logfile: pialert_update_2023-10-01_06-55.log

- Checking Python...
Python 3 is installed on your system
mac-vendor-lookup is already installed
fritzconnection is already installed
routeros_api is already installed
unifi is already installed
- Stopping Pi.Alert...
No timeout is set. Pi.Alert restarts itself with the next scan after 10min.
arp-scan: no process found

Pi.Alert  (2023-09-26)
---------------------------------------------------------
Current User: root 


Test Reporting...
    Skip mail...
    Skip PUSHSAFER...
    Skip PUSHOVER...
    Skip Telegram...
    Skip NTFY...
    Save report to file...

DONE!!!


Configured Pi.Alert scans are disabled

- Reset permissions...
- Deleting previous Pi.Alert backups...
- Creating new Pi.Alert backup...
........................................................................................
- Cleaning previous version...
- Checking packages...
- Downloading update file...
/opt/pialert_latest.tar         100%[=======================================================>]  86.04M  9.57MB/s    in 9.5s    
- Uncompressing tar file
.......................................................................................
- Deleting downloaded tar file...
- Generate autocomplete file...
- Copy autocomplete file...
- Config backup...
- Updating config file...
- Updating DB permissions...
- Installing sqlite3...
- Set Permissions...
chmod: cannot access '/opt/pialert/back/speedtest/': No such file or directory

[ERROR] in line 56: exit code 1: while executing command update

root@pialert:~#