• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Apple devices loading default certificate instead of domain-specific one

Oldiesmann

Basic Pleskian
Over the past week or so, I've been getting reports from users on one of my forums that they are no longer able to access the site from their iPads.

Tonight with the help of a friend, we were finally able to track down the issue - iOS is trying to load the default security certificate rather than the one associated with the site itself, and then refusing to load the site since the security certificate was issued for the server's hostname, which is different than the domain this site is hosted on.

Given that this is only happening with iOS devices and I haven't changed anything with regards to the security certificates on the server, I'm guessing that it's an iOS issue, but I was wondering if anyone else is having this problem or if there's anything I can do to get around it.

If it makes any difference, Plesk is set to redirect from http to https automatically and all domains are secured with a free Let's Encrypt certificate (the default one is also a Let's Encrypt certificate, from the server pool).
 
Managed to get to the bottom of the problem it seems. I have nginx set up as a reverse proxy with Apache and recently enabled http2. Apparently this is causing nginx to send an upgrade header, which in turn causes problems for Safari/iOS. Adding "proxy-hide-header: upgrade;" to the nginx configuration fixed the issue.
 
Back
Top