You’re offline. This is a read only version of the page.
Announcements
62
I am trying to connect to a BC on-prem system using the Business Central Android / iOS app. The certificate is self-signed - I followed the instructions described here: How to get Microsoft Dynamics NAV for tablets to connect using a self-signed certificate.
However, I am getting the error message "Server connection timeout occurred."
I am able to connect using a browser rather than the app. And I've previously used the same phone to connect to NAV systems using the NAV Android app and a self-signed certificate.
So my question is, does the BC app not allow connections using self-signed certificates?
Thank you in advance for any suggestions.
Chris
Hi Carles,
Unfortunately I never managed to get it working with a self-signed certificate. At the time I didn't look into it much further since I was only testing for my own purposes, not a customer's.
Anyway having just tried again, I noticed that after installing the certificate on my Android phone, it appears in "User Credential" rather than "Trusted Credentials\User". I understand that the certificate needs to appear in "Trusted Credentials", so I my guess is that this is the reason for the problem.
App developers can opt to trust a custom CA by including it in their app's configuration file. See:
developer.android.com/.../security-config
stackoverflow.com/.../list-certificate-stored-in-user-credentials
But I could not find a way for a user of an existing app to do the same thing. My phone has some old self-signed certificates in "Trusted Credentials\User" but I am not sure how I installed them there.
I wonder if your case is the same?
Regards,
Chris
Hi Chris, I'm in the same case. Did you manage to fix it?
Regards,
Carles
Hi,
please check the certificate which you installed is right one.
i too had this problem, i just deleted installed certificate from my Phone also searched and deleted certificate .cer file from android phone and tried again it worked for me.
Hi Vigneswaran,
Thanks for your help.
My certificate indeed was missing the Subject Alternative Name, so I created a new certificate as you described and confirmed that it did include SAN (DNS Name=certauth.fs.<my domain name>). But unfortunately, when I tried to connect with the Android app, I got the same error as before.
I will have to do some further experimentation/investigation. I wish the app would show a more detailed error message instead of the catch-all of "connection timed out" !
Regards,
Chris
Hi Chris,
this might be because of the SAN (Subject Alternative Name) in your Certificate
There is a change in Command for Generating the Self Signed Certificate, use below command to create New Self Signed Certificate and use it for Connecting Mobile / Tablet Client
New-SelfSignedCertificateEx -Subject ‘CN=<IP/Domain>’ -IsCA $true -Exportable -StoreLocation LocalMachine -SubjectAlternativeName certauth.fs.<IP/Domain>, <IP/Domain>
More Info : cetastech.com/.../certificate-changes-for-your-nav-mobile-client
#1
André Arnaud de Cal...
294,095
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
