Telegram send

[te0203]

Hello. I am setting up sending messages from the Pi.Alert application. Sending works from the command line, but not from the web panel. Where can I see the logs of the shoutrrr package? Apparently, the web application does not have permission to run the file...

`# Shoutrrr

----------------------

SHOUTRRR_BINARY = 'x86'

SHOUTRRR_BINARY = 'armhf'

SHOUTRRR_BINARY = 'arm64'

SHOUTRRR_BINARY = 'x86'

Telegram via Shoutrrr

----------------------

REPORT_TELEGRAM = True
REPORT_TELEGRAM_WEBMON = True
TELEGRAM_BOT_TOKEN_URL = 'telegram://625xxx8585:AAGOxxxfrKD3f6mib3j0S_DV6bxx1JuguE@telegram/?chats=106368xxx92&preview=No'
`

[leiweibau]

The web application does not require any rights for shoutrrr, as the backend user sends the notifications. To my knowledge, shoutrrr does not generate logs. When you say it works from the command line, do you mean sending directly via shoutrrr, or via ./pialert-cli reporting_test

[te0203]

I have the application installed in a Proxmox LXC container. https://community-scripts.github.io/ProxmoxVE/scripts?id=pialert
The container developers placed the application in the /opt/pialert directory
If you go to the /opt/pialert/back/shoutrrr/x86 directory and run the command
'
./shoutrrr send
--url "telegram://6252188585:AAGOiXXXfrKD3f6mib3j0S_DV6bxx1JuguE@telegram/?chats=1063XXX692&preview=No"
--message ""
'
then the message is sent, but there is no message from the web interface. And there are no messages to the user that an error has occurred in the web interface.
Everything is fine there, but the messages are not sent.
I followed the chain to the script /opt/pialert/back/pialert_reporting_test.py
When I run the script, it gives an error that python is not found.
I checked the python version in the python3 environment.
I installed the python-is-python3 package.
It started to run and gives a configuration file error that there are keys without values.
I filled in the empty keys with ''.
The entire application crashed. It does not scan.
'
Scanning...
arp-scan Method...
arp-scan: Multiple interfaces
Pi-hole Client List Method... Skipped
Pi-hole DHCP Leases Method... Skipped
Fritzbox Method... Skipped
Mikrotik Method... Skipped
UniFi Method... Skipped
Satellite Import... Skipped

'
The container developers said that the problem is not with them.

[te0203]

Took the original file https://github.com/leiweibau/Pi.Alert/blob/main/config/pialert.conf
Reworked to fit the entire script layout
If you disable ICMPSCAN_ACTIVE, it gives an error.
When enabled, error is

'
Pi.Alert v2024-11-11

Executing user: root
Timestamp: 2024-11-12 05:57:00

Retrieving Internet IP...
Traceback (most recent call last):
File "/opt/pialert/back/pialert.py", line 3974, in
sys.exit(main())
^^^^^^
File "/opt/pialert/back/pialert.py", line 94, in main
res = check_internet_IP()
^^^^^^^^^^^^^^^^^^^
File "/opt/pialert/back/pialert.py", line 199, in check_internet_IP
internet_IP = get_internet_IP()
^^^^^^^^^^^^^^^^^
File "/opt/pialert/back/pialert.py", line 546, in get_internet_IP
cmd_output = subprocess.check_output (curl_args, universal_newlines=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/subprocess.py", line 466, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['curl', '-s', '']' returned non-zero exit status 3.
'

Doesn't want to scan yet.

[te0203]

added QUERY_MYIP_SERVER = 'http://ipv4.icanhazip.com' into pialert.conf file

root@pialert:/opt/pialert/back# ./pialert.py internet_IP

Pi.Alert v2024-11-11

Executing user: root
Timestamp: 2024-11-12 07:06:00

Retrieving Internet IP...
195.64.239.58

Retrieving previous IP...
195.64.239.XX
No changes to perform

Skipping Dynamic DNS update...

Continuous New Device Notification...
Skipping... Not activated!

Auto Speedtest...
Skipping Speedtest... Not activated!

Auto Update-Check...
Crontab: 0 3,9,15,21 * * *
Version Check function was NOT executed.

Auto Backup...
Skipping Auto Backup... Not activated!

Cleanup Reports...
Skipping Cleanup Reports... Not activated!

DONE!!!

[leiweibau]

Yesterday I released a new version which, depending on the configuration, has new dependencies in the configuration file.
First of all, I would recommend that you install the update so that I can assume a defined version for support.

Follow these instructions for an update within the LXC Contianer
tteck/Proxmox#3119 (comment)

Which OS will be installed in the LXC container?

Next, I would ask you to execute the command /opt/pialert/back/pialert-cli reporting_test, as this is the command that the web interface executes for a test notification. You are right in your observation that the web interface does not give any feedback about errors, it only gives feedback that the command has been called.

Using a sudoer file, I grant the web interface (user: www-data) the corresponding right to execute pialert-cli. Please check the file /etc/sudoers.d/pialert-frontend to see if the path to pialert-cli is correct or exists.

The package “python-is-python3” should not be necessary.

In my test environment, I can't see any abnormalities in the Telegram notification. All messages are delivered

[te0203]

Update -> install.
LXC Contianer -> debian
/opt/pialert/back/pialert-cli reporting_test -> OK
/etc/sudoers.d/pialert-frontend -> OK (www-data ALL=(ALL) NOPASSWD: /opt/pialert/back/pialert-cli)

After replacement QUERY_MYIP_SERVER = 'http://ipv4.icanhazip.com/' into pialert.conf file everything works.
Thanks for help.