Issue:
Android devices no longer performing automatic mail syncing.
Domino console with Traveler 14.0 or earlier, show Traveler error:
NTS_PUSH_FCM_RETRY_EXHAUSTED 0= ... Exception Thrown: java.io.IOException: Could not send message ...
Domino console with Traveler 14.0 FP1, show Traveler error:
Exception Thrown: com.google.auth.oauth2.GoogleAuthException: Error getting access token for service account: Connection reset by peer, iss: ...
Running Traveler 14.0.0 or Earlier - Resolution:
Upgrade to Traveler 14.0.0 FP1 (14.0.0.1) or higher.
Firebase Cloud Message (FCM) push notifications are now using Google FCM HTTP v1 API. Google discontinued support/use for the old one.
See HCL support KB0115437 for more information.
Running Traveler 14.0 FP1 or Later - Resolution:
The token renewal request for the FCM API may not be properly making through a reverse proxy.
See HCL support KB0115978
Basically, the tech-note covers how to tell Traveler's Java process where/how to push through the corporate reverse proxy:
- Administrator client --> Domino Traveler server (left bar server list) --> Server (tab) --> Status (sub-tab) --> Server Console (left menu option)
- In the Domino console:
> set config NTS_JAVA_PARMS_EXT=JAVA_PARMS_1
> set config JAVA_PARMS_1=-Dhttps.proxyHost=myproxy.mindwatering.net -Dhttps.proxyPort=2345
Note:
- Update proxy host's internal FQDN and port for your environment.
Alternate to Upgrading an Old Traveler:
If the users do not mind manually syncing, the use of the legacy FCM can be disabled in earlier releases of Traveler by disabling FCM push in the notes.ini.
- Administrator client --> Domino Traveler server (left bar server list) --> Server (tab) --> Status (sub-tab) --> Server Console (left menu option)
> set config NTS_PUSH_ENABLE_FCM=false
As a reminder, this will not fix the problem, but turn off the error message and still require users manually sync.
previous page
|