Android GCM (FCM) notification broken on modern Linux

[nureinmudhir-collab]

for aomw reason since the 6th of april the app is not sending notifcations through to the phone not for charging starting nor for charging stopping. it does show me the vehicle is charging or has stopped charging whilst looking st the app and all controls like door locking and climate control work fine. also ocasionally the vehicle will not stop charging I think I have fixxed that issue but the notifcations are still not comming through. please help.me fix this as Main reason i got this is to keep an eye on the car if anything goes wrong through notifications at public chargers so i can go back to my car to reinitiate charges

[dexterbg]

@markwj Possibly a side effect of the server migration?

@nureinmudhir-collab Please try switching to my server (ovms.dexters-web.de) -- I see you already set up an account, so should be easy to switch.

[nureinmudhir-collab]

what is server migration did try your server initially but could figure out how to set it up on the ovms it kept not connecting. or I coulsnt get it to connect I have kind of forgoton the login information I put for your server aswell. it was working fine on the ovm server initially. I have a Env200 and I had to remove the tcu telematiks cable to be able to use climate control. this issue only came about as i realised my car mic was no longer working so followed instructions by pulling out 2 cablew only instead of the whole harnes theire after this issue started. the vehicle also has issues figuring out when to stop the charge once it reaches 98% due to it not getting notifications on the app i think the 2 are connected

[nureinmudhir-collab]

@markwj Possibly a side effect of the server migration?

@nureinmudhir-collab Please try switching to my server (ovms.dexters-web.de) -- I see you already set up an account, so should be easy to switch.

I tried again with the dexter server it doesnt connect for some reason not sure what ive done wronf on their would apreciate if you coild run me through how to connect it. so on the ovms module login system the ip adress place it does say connected but when i put the credentials in the app it doesnt connect for some reason just keeps saying connecting.

[dexterbg]

Mark had to migrate all openvehicles.com services to a new server on the 6th of April, so matching your issue. Due to the new OS environment, he ran into problems, which still are not fully solved, and the push notifications may be one of them.

Regarding setup for my server, I already replied to your email. If you still can't get it to work, send me the output of command module summary.

[dexterbg]

The App should connect regardless of an existing module connection. Here's my (slightly outdated) FAQ image on the data input:

[nureinmudhir-collab]

All sorted so solution of changing server to dexters has done the JOB

[markwj]

Seeing issues running on Rocky10 / OEL10:

2026-04-09 12:01:03.487698 +0000 error OVMS::Server::PushGCM: - - 20220100 msg gcm fork_call error : RSA.xs:983: OpenSSL error: illegal or unsupported padding mode at /usr/local/share/perl5/5.40/JSON/WebToken/Crypt/RSA.pm line 22.

Note that JSON::WebToken is v0.10 and is more than 10 years old.

Seems others have moved to CryptX: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/98711

[nureinmudhir-collab]

Seeing issues running on Rocky10 / OEL10:

2026-04-09 12:01:03.487698 +0000 error OVMS::Server::PushGCM: - - 20220100 msg gcm fork_call error : RSA.xs:983: OpenSSL error: illegal or unsupported padding mode at /usr/local/share/perl5/5.40/JSON/WebToken/Crypt/RSA.pm line 22.

Note that JSON::WebToken is v0.10 and is more than 10 years old.

Seems others have moved to CryptX: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/98711

So what do I need to do to fix the issue how do I make the move and will that fix the issue

[markwj]

So what do I need to do to fix the issue how do I make the move and will that fix the issue

At the moment the issue only seems to be affecting the newer api.openvehicles.com server. Dexter's EU server is running older versions of OpenSSL so doesn't seem to be affected.

We will work on patching the library used on api.openvehicles.com to resolve this for users on that server. But at the moment we have a number of issues on that new server that we are addressing, so this is not a simple/quick fix.

[nureinmudhir-collab]

So what do I need to do to fix the issue how do I make the move and will that fix the issue

At the moment the issue only seems to be affecting the newer api.openvehicles.com server. Dexter's EU server is running older versions of OpenSSL so doesn't seem to be affected.

We will work on patching the library used on api.openvehicles.com to resolve this for users on that server. But at the moment we have a number of issues on that new server that we are addressing, so this is not a simple/quick fix.

so today when i set it on the app to 98% aftee the glirch came back of it not stopping the charge on env200 after 2 minutes or so it stopped .so usually when it gets to 98% on the app it glirches and changes end time to random timings from 2 to 6 hours for the remining 2 percent.
my question is the parch your doing in the library will it fix this issue.

[nureinmudhir-collab]

So what do I need to do to fix the issue how do I make the move and will that fix the issue

At the moment the issue only seems to be affecting the newer api.openvehicles.com server. Dexter's EU server is running older versions of OpenSSL so doesn't seem to be affected.

We will work on patching the library used on api.openvehicles.com to resolve this for users on that server. But at the moment we have a number of issues on that new server that we are addressing, so this is not a simple/quick fix.

Oh you was talking about the notifcation issue i thought you was talking about the charging stopping issue

[dexterbg]

Seems others have moved to CryptX: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/98711

CPAN doesn't have the patch yet, let alone any RHEL based distribution.

The alpine package now does have the patch:
https://pkgs.alpinelinux.org/package/edge/community/x86/perl-json-webtoken
… but the build log shows they skipped the RSA tests …

t/02_rsa.t ..................................................... skipped: Test requires module 'Crypt::PK::RSA' but it's not found
t/spec/draft-ietf-jose-json-web-signature-08-A2.rsa_sha256.t ... skipped: Test requires module 'Crypt::PK::RSA' but it's not found

… and the source reference is the xaicron github account, which doesn't have the patch yet… :-/
The fork https://github.com/timlegge/p5-JSON-WebToken has the patch.

So, patch/build locally?