HTTPS not working about photoprism-android-client

[ally9696]

During the login this error
"CertPathValidatorException: Trust anchor for certification path not Found."

ROOT CA> INT CA > User Certificates into one Cert files.
Fixed the issue and its no longer giving the login error.

[ippocratis]

Maybe this?
wallabag/android-app#516 (comment)

I use caddy which handles lets encrypt certs automatically so I don't have to worry for intermediate certs, renewal's etc

[Radiokot]

Great! Thanks to everyone joined the investigation

[Radiokot]

Hi.
I'm sorry you have this weird issue. We'll try to figure it out.
I, too, use Let's Encrypt certificate for test environment running behind nginx and it works fine. The error seems specific to your setup, it would be helpful if you emailed me your library URL (without credentials), so I could try to connect to it myself.
[email protected]

[leosamuele221]

Probably it's specific to your setup.
I also have my photoprism hosted with https, my certificate is provided by let's encrypt and i have no problems

[ally9696]

[ally9696]

I guess some hints are out, let me try

[ippocratis]

So most likely you have to fix intermediate certs for your reverse proxy

[ally9696]

I guess i need to add the intermediate SSL inside the cert where the header and footer ends to complete the trust chain..

[ally9696]

Could this be a solution..

[ippocratis]

I'm not that technical ,
Cant help with that, sorry
As I said caddy does all the job for me

[Radiokot]

@ally9696 make sure in your server configuration you use the full chain file and not just the standalone certificate. For nginx it looks like this:
ssl_certificate /etc/letsencrypt/live/radiokot.com.ua-0002/fullchain.pem; # managed by Certbot
and the fullchain.pem file contains multiple certs one by one, like this:

-----BEGIN CERTIFICATE-----
MIIFwzCCBKugAwIBAgISBLw/vgERGMn8PYv32H4uVgJPMA0GCSqGSIb3DQEBCwUA
...xxx...
McnduECERMvk55VnhXoDzMsfz0htoUNWVAeaQoDov0dKx6Ez+Qkm
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
...xxx...
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIFYDCCBEigAwIBAgIQQAF3ITfU6UK47naqPGQKtzANBgkqhkiG9w0BAQsFADA/
...xxx...
Dfvp7OOGAN6dEOM4+qR9sdjoSYKEBpsr6GtPAQw4dy753ec5
-----END CERTIFICATE-----

[ally9696]

I guess i need to add the intermediate SSL inside the cert where the header and footer ends to complete the trust chain..

Yes will try this out since i didn't configure the server with the full chain. Ill merge the certificate and wait for ssl cache to clear.