Notifications API Key.

¿Might there be a problem with my api key?

I'm not receiving notifications whatsoever.

I had everything working, some day telegram notifications started to fail, now I don't even have the app (traccar manager) notifications, not even using the test notifications button.
I'm trying on my production server, Traccar 5.12 (Linux x64) and on my test server, Traccar 6.1 (Linux arm x64)

This appeard in the log of my test server.

2024-05-22 21:52:41  WARN: Push user 2 error - Authorization error

Thanks

This appeard in the log of my test server.

2024-05-22 21:52:41  WARN: Push user 2 error - Authorization error

This is the production server log.

2024-05-22 21:58:21  INFO: HikariPool-1 - Starting...
2024-05-22 21:58:22  INFO: HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@7ac0e420
2024-05-22 21:58:22  INFO: HikariPool-1 - Start completed.
2024-05-22 21:58:22  INFO: Clearing database change log checksums
2024-05-22 21:58:23  INFO: Successfully acquired change log lock
2024-05-22 21:58:23  INFO: Successfully released change log lock
2024-05-22 21:58:23  INFO: Successfully acquired change log lock
2024-05-22 21:58:23  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2024-05-22 21:58:23  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2024-05-22 21:58:24  INFO: Reading from rastreo.DATABASECHANGELOG
2024-05-22 21:58:25  INFO: Reading from rastreo.DATABASECHANGELOG
2024-05-22 21:58:25  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2024-05-22 21:58:25  INFO: Successfully released change log lock
2024-05-22 21:58:25  INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2024-05-22 21:58:26  INFO: Operating system name: Linux version: 4.19.0-26-amd64 architecture: amd64
2024-05-22 21:58:26  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.13+8-LTS
2024-05-22 21:58:26  INFO: Memory limit heap: 239mb non-heap: 0mb
2024-05-22 21:58:26  INFO: Character encoding: UTF-8 charset: UTF-8
2024-05-22 21:58:26  INFO: Version: 4.15
2024-05-22 21:58:26  INFO: Starting server...
2024-05-22 21:58:26  INFO: jetty-10.0.7; built: 2021-10-06T19:34:02.766Z; git: da8a4553af9dd84080931fa0f8c678cd2d60f3d9; jvm 11.0.13+8-LTS
2024-05-22 21:58:27  INFO: Started o.t.w.@349312d5{/,null,AVAILABLE}
2024-05-22 21:58:27  INFO: Session workerName=node0
2024-05-22 21:58:27  WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2024-05-22 21:58:28  INFO: Started o.e.j.s.ServletContextHandler@99223ac{/,null,AVAILABLE}
2024-05-22 21:58:28  INFO: Started ServerConnector@250a500b{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2024-05-22 21:58:28  INFO: Started Server@5e37fb82{STARTING}[10.0.7,sto=0] @7190ms
2024-05-22 21:58:28  INFO: Health check enabled with period 480000

Just checked, and the app (Traccar manager) has the proper permissions for notifications in Android. But no notification ever appears, only screen banner (eventTest) but no proper notification.

up

Production server is 4.15, my mistake.
Last version without modern interface enabled.

Just made it work in test server, version 6.1

I achieve it by NOT using the "-" before chat id parameter under users... And by NOT using the "bot" characters before the telegram key under traccar.xml...

Who would have tought... RIGHT THE OPPOSITE as it's recomended in the current available instructions. As ussual.

Still can't make it work on 4.15 version, so I guess, IT IS because my notifications API key somehow is disabled....

...

So... ¿how could I find if my API key is disabled from Traccar forum side?

so.. still nothing

So, it must be disabled then. I wonder why.