Hi, I have installed certs SSL Comodo, I followed the guide on the Carbonio documentation...all ok, but have this problem:
if I go to administration login, have https and working fine...I enter as administrator and https working fine. After logout i try https://mailserver.tld/static/login and have https, login with email and password and have always https, if click in one email not have https...how is possible ?
Thank you for suggestions
Cal
Could you please elaborate on the issue a little bit?
It will help us to understand the problem clearly.
Regards,
Hi @shariful-islam sorry for my poor english...
if I log in in admin area have https ( screenshot)
If login as client have https: (screenshot)
but after login if click in email for read not have ssl ( screenshot)
how is it possible that emails are not protected by ssl ?
thank you
Cal
Yes, I see your certificate is okay.
Let us check and meanwhile can you check it in all browsers and let us know your feedback.
Regards,
Hi @shariful-islam , in all browser have identical problem... chrome, fireworks and edge
Other question not possible view your attachment: You are not permitted view this attachment ....why?
Thank you
Cal
Hello @calogero
I tried to reproduce it in the latest version of Carbonio (Release 22.5.1 Community Edition.) but I couldn't.
No mixed content or HTTP request has been found.
Please check that you have the latest version too, if the issue still occurs, I suggest tracing the requests with the dev tools of your browser to find the HTTP req and report it here so we can further investigate.
Hope this helps.
Hi @matt, initially when I installed Carbon CE I also installed Let's Encrypt, I thought the problem stemmed from the let's Encrypt certificate And I purchased an SSL Comodo, but the problem still persists
I have also noticed a great difficulty among my clients in setting up mail on Apple devices, why the certificate is not accepted
I will try to perform more checks but the ones I performed do not detect errors.
Thank you and have a great day
Cal.
@calogero I'm not sure the issue resides in the certificate itself, but in part of the content that is requested via HTTP instead of HTTPS (mixed content), this is why I suggested analyzing the requests with the browser's dev tools (network tab).
If you want to exclude issues related to the certificate or its configuration, you can use SSL Labs.
