There is one but the hostname / ip address would not match your server. Many browsers would refuse to display with a mismatched certificate fearing a man-in-the middle attack.
But why is it accepted just at first time? Found out that it is not depending on the admin login - happens everytime i close the “app” and open it again.
In generell there should be no problem with the certificate - before changing the ip it worked already.
Is it possible, that the path to the cert changed in oh3 and the path in docs isnt correct anymore?
connecting to a https site via browser you can examine the certificate that is being used on the server site. Doing this you should be able to identify if your latest version of the certificate is being used.
I agree that in case of an invalid certificate you at least should be able to see a warning message of the browser that the site is not being trusted - and - in that case the initial connection needs to show the same behavior.
There are different certificates being used in OH.
One in case you use a reverse proxy ( e.g. nginx ) and one in the keystore.
Which one did you change resp. how do you want to use it ?
Additional info:
When i just close the tab and open a new one (without deleting browser data) on my mobile, the site is loading again - until i close and reopen the browser again.