Actually there was a similar problem when trying to install a certificate on the site. Domain from 2domains, DNS server was from jino. And when trying to access HTTPS, all browsers issued that the certificate was expired, issued by some internet widgits pty ltd, although it was taken in a completely different place and on a different date.

Then it turned out that even if you finish the Apache at all, or configure it for port 80 and disable SSL (and reboot!), And try to log in via https: // it will still be like that.

And I notice similar nonsense on other foreign sites where HTTPS does not seem to be supported, but there is some expired certificate on https: //. This was on 3 sites out of 5, on the other 2 it was either timed out or refused.

The question is - where does it come from?

Particular emphasis: from the browser (or rather, HTTP-client with SSL) and the client provider does not depend entirely.

  • If you really turned off SSL and made sure that port 443 is not busy by anyone and at the same time https starts to establish a connection and gives the wrong certificate, then there are only 2 options: either you are using the wrong machine where you are changing the settings for Apache, or something wedged into the chain between sending the request and arriving at the server. This could be some kind of proxy included in your web-client, a separate software on your machine, or traffic is intercepted somewhere along the way from you to the server - Mike
  • @Mike on the client is definitely nothing, I told you. ALL customers issue this, even online services. the car is exactly that. I will even try to change the server IP in dns records later. - Water Snake
  • one
    "Other foreign sites" can be arranged completely differently, so there is nothing to put them here. You better tell more about yourself - which server, which apache, is there exactly 443 missing in all apache config files, and so on - andreymal

1 answer 1

Many companies providing hosting services (from shared to VDS) have their own systems that simplify the deployment of servers from virtual machine images. Once an image of the system is made, in which all the necessary packages are put and then the deployment takes dozens of times less time. No errors, savings on staff, an increase in the company's financial indicators.

So, quite often I saw a situation when the same image was used for more than a year, which leads to the fact that the SSL certificates sewn into the image have time to rot beforehand.

It looks like your case.

What and how it is configured inside the car - you need to understand each case, and you did not bring this information. It's a pity.

Well, first of all, find out who is listening to port 443 on your machine: if it is not an Apache (in the off state, the same certificate continues to be shown), then some nginx or something else similar.

Give the command:

netstat -natp

And read her conclusion.

Do you have a full-fledged hosting, with root or is it still shaded with some kind of self-written panel?