This does not fix the issue.

I have a later version of PRTG for Android, as this Article is from June. I'm running version 16.3.2

I have deleted the app and removed it.

I ran the batch file which created the dh.pem file. I then stopped the core servers and rebooted the OS. Once the OS booted back up and the core servers started. I tried again and I continue to get the same error “could not retrieve passhash”.

This is really getting frustrating. I understood during the beta preview of Android N that there would be issues. But this is the full released version of Android 7.0.

Hello,

Which exact PRTG Core Server version are you using?

Are you referring to the version Installed on the computer/web?

That would be 16.3.25.5767 Latest Android version is 16.3.2

This doesn't work because your OpenSSL implementation is broken (Maybe path missing somewhere?).

When I try to create the PEM using the batch file, the following is written to the log file;

5768:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c:175:fopen('D:\Projects\libraries\openssl\openssl-1.0.1t\00_openssl_binaries_32/ssl/openssl.cnf','rb') 5768:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:180: 5768:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:197:

Hi Rod,

Which version of PRTG are you running? Also how does the generatedh.bat look like? It should contain something like this:

set OPENSSL_CONF=.\openssl.cnf ..\openssl.exe dhparam -out dh.pem -2 1024 2> dh.log

Kind regards,

Erhard

Hi, I'm having the same issue whit the PRTG android app sine upgrading to Android 7. Getting a "handshake" error on existing account. if I remove account on app and try to add a new one it show "error with SSL".

PRTG Server is fine and app works on other devices (IOS and Android) without issue. It's only since upgrading to Android 7 Nougat on Samsung S6 that the issue occurs. I tried the DH option in previous posts, restarted PRTG core and no difference. Running latest version of PRTG 17.2.30.1825

Hi there,

Make sure that you start the BATCH file as an administrator. If done, leave the command window opened till it finishes. Should an error occur, forward us a screenshot and the created log within the directory. Please also make sure that the PRTG Core Server is restarted once afterwards.

Best regards.

I'm having exactly the same issue.

Server is running 17.2.30.1825

The app was running fine until I received an update to android n (galaxy tab s2), then the app would not connect. My phone running android m connects fine.

I have regenerated the dh file as above (there was already a dh file) as administrator and rebooted the server, but no joy.

I just get "An SSL error has occurred" when I re-create the account.

Hi there,

I am afraid that this topic is not the best for the Knowledgebase. Please open a new support ticket by submitting a support bundle to us. This can be done via the "Contact Support" ribbon in the lower right corner of the web interface. If the server has no internet connection you can mail us via [email protected].

Best regards.

I am having the same problem. The error message points to this knowledgebase article. If there is another knowledgebase article for this problem could we get a link to it?

Hi there,

Make sure that you start the BATCH file (to generate the dh.pem) as an administrator. If done, leave the command window opened till it finishes. Should an error occur, post the content the created log within the directory. Please also make sure that the PRTG Core Server is restarted once afterwards.


Best regards.

I have started the batch file and it is still running, but as with some of the other posts above I don't think it will fix the problem. I am running server version 17.1.28.1032+ and the error started with the latest Android update on my Galaxy S6. I know this is probably a different problem and should be separated from this knowledge base article, but the error message gives a link to this page. If there is somewhere else for this information could we get a link to it?

Hi there,

The issue is, that Android 7 has some improved security features which require ECC (Elliptic curve cryptography) on the webserver of PRTG. To use this, you have to generate the DH.pem. The generation will need some time, depending on the hardware and current load. After you have successfully generated the DH.pem, you have to restart the PRTG Core Server Service.


Best regards.

Hi,

I'm having the exact same problem.

I'm unable to create account with my Huawei (android 7.0) while colleagues with other versions or iPhone have no problem.

I tried the above twice (generated dh.pem, with 1024 or 2048 bits key and restart PRTG core, with no effect).

No error in ph.log neither ....

Hi there,

What exact errors do your colleagues exactly get on the Huawei? Is it "An SSL Error occured.." errors that is displayed on login?

Best regards.

Is there any update/fix for this issue? I am running Android 7.0 and I too all of a sudden was not able to access my PRTG installation from my app. I uninstalled and reinstalled the app and now I cannot log in from the app at all. I keep getting the error message "I could not retrieve the passhash. Perhaps your password is wrong?" (my password is definitely correct as I can log in from a browser). My PRTG core server has the dh.pem file with a modified date of 3/31/2016, so it has been there for awhile. I'm running version 17.3.32.2478. It sounds like there may be other issues preventing login from Android 7.0, please help.

Hi craig,

Please open a browser on the phone and try to connect to the webinterface of PRTG, does that work?

Best regards.

Same problem, get an SSL error but can login via a web app on the phone

Hi there,

Have you tried the steps in the mentioned KB-Article? Even if the first look indicates that the KB-Article is unrelated to the problem, it is actually the solution. In newer PRTG versions we implemented ECC (Elliptic curve cryptography) which creates issues on Android 7 devices. Therefore you have to generate the DH.pem as described in the article. Pleas make sure that you start the BATCH file as an administrator. If done, leave the command window opened till it finishes. Should an error occur, forward us a screenshot and the created log within the directory. Please also make sure that the PRTG Core Server is restarted once afterwards.

Should this not work, try the following commands:

• open a command line (cmd.exe) as an administrator
• issue the following commands:
  cd "C:\Program Files (x86)\PRTG Network Monitor\cert\"
  generatedh.bat
  
  Best regards.

I was just struggling with this and I did run the bat file to generate the new dh.pem file. I was waiting for aa few hours until we could restart the server.

However, a colleague showed me the option to use the QR barcode from the web interface to set up an account in the Android app. I used that within the Android app and for some reason my password was accepted this time without the complaint about a "passhash" issue. I can't say why it worked but try it if you are struggling.

My phone is Android Nougat ( N or 7.x ) and we are on 17.x version of PRTG.

A few days ago stopped with this error on my Samsung S8+ 8.0. S9+ without any problems. I've tried today upgrade to latest version, no difference. I've been tried generatedh.bat with restart, no change. I've tried move to builtin certificate from Paessler and generatedh.bat and restart, still no success. S9+ works in all cases. I think that a few days ago was Android application upgrade, so I think there is an error in it.

Hello Vaclav,

I've just tested on my end with the current PRTG app version, last updated on May, 4th according to Google Play store and it worked without issues (Huawei P9, Android 7.0). I'll talk to the dev, he should be able to provide a debug version to analyze this further.

Kind regards,

Erhard

Hello Vaclav,

We need a few more details to analyze this, I'll send you an email about it.

Kind regards,

Erhard

Registered to say that this solution worked quickly and perfectly! Thanks support and devs :)

1. On your PRTG core server system, navigate to the \cert subfolder of your PRTG program directory.
2. Check if the file dh.pem is in this folder.
3. If you cannot find dh.pem, execute the script generatedh.bat in the same folder to generate dh.pem.
4. Restart the PRTG core server.

same problem here, but solved with earlier mentioned solution:

... the option to use the QR barcode from the web interface to set up an account in the Android app. I used that within the Android app and for some reason my password was accepted this time without the complaint about a "passhash" issue. I can't say why it worked but try it if you are struggling.

Strange but true, QR barcode from My Account page help to avoid this problem for me.

I use nginx as reverse proxy and connected with Android 9. Had the same Problem as u guys. My solution was to add following cipher to my ssl_ciphers > ECDHE-RSA-AES128-GCM-SHA256. PRTG Version 19.3.51.2830+ using only TLS1.2. App Version 19.2.2.1

Ran into the issue with the passhash and been pretty frustrated. I have a few PCs on my net and they all connect fine. Not quite sure why the issue persists as I mostly see android 7.xx complaints and my phone is the new OnePlus 7 Pro running android 9 Oxygen OS. I should mention now that I, in no way, shape, or form, know alot about network tasks and such but I know enough to set up PRTG to monitor my home network. If anyone has a fix for Oxygen OS/Android 9 I'm all ears.

You can try to scan QR-code as i mentioned above, you can find this QR-code on the page inside PRTG Web-Interface: Setup -> Account Setting -> My Account -> Show QR Code for Mobile App Login. This code need to be scan direct from the menu inside Android App. Since my last post a year ago i have no any problem to login into application from Android or iOS smartphones.

@vasiliy Thanks for chiming in!
@puddlejumper6999 Please let us know if you run into issues using the QR code instead.

Same problem here, and solved by re-generating the SSL cert. The Android phone wont ask for installing the cert until I re-generated it. Then works. Thank you.