That’s quite possible. If your hosting provider is managing the certificate for you, it’s possible that they have a backlog of certificates they work through and it took a while for yours to get to the front of the line. Or maybe they have a scheduled job for this thing that only runs every once in a while.
That’s a tough one to answer in a way that covers every site and environment out there, so if you could go into detail on the kind of software you’re running and what you’re trying to achieve, someone could probably give you more specific advice.
If your host has an option to redirect all HTTP requests to HTTPS, that would be a good start. You might also be able to add a
.htaccess file to do that, if your host supports that and uses apache. A quick search brought up this page which has a
.htaccess snippet at the bottom that seems to work for your host.
https://, or you might get mixed content warnings or semi-broken pages depending on your browser. If you use a CMS like WordPress, there are probably existing settings and plugins that help with portions of this.