Sorry, but that is complete misinformation. I automated the Let's Encrypt SSL certificates and they work fine. I was then asked to use a multi-year commercial certificate on the servers, but I pointed out that they were no longer available from reputable suppliers as current standards say that SSL certificates must be renewed annually. I was not believed for a while until Michael finally looked it up and realised what he was asking for was not possible and the subject was dropped. There was no subsequent request to move the SSL Cert process anywhere else or change the process in any other way.

There was no time bomb placed in the SSL Cert process. It is just that Clearcenter have not a clue on what runs on their servers. When AWS shut down the Clearcenter servers for non-payment in October, they paid the bill and then selectively restarted various servers. This is when all the DDNS and Domain system also failed. They also decided not to restart another of the servers which, among other things, looks after the certificate renewal. I don't think they have any idea of the other services provided by that server.

@Michael, I request that you retract your post.

This could be a taste of what is to come. AWS shut down the Clearcenter servers yesterday (which includes the forums so take note of this post manually, don't bookmark it). Presumably the bill was eventually paid but not everything has come back up. If it happens permanently, things you could do to help yourself:

1 - move out of the way /etc/yum/pluginconf.d/clearcenter-marketplace.conf
2 - install ntp as this overrides the timesync app, or edit /etc/clearos/date.conf and put in your favourite time server, perhaps using a more local one like 0.uk.pool.ntp.org for me.
3 - The clearsdn.com domain will go down, try adding a line to a file you create (with any name you want) in /etc/dnsmasq.d/ with:Then restart dnsmasq. I didn't get to fully test it yesterday, but it may sort out the unresponsive webconfig. Don't do it unless you have done 1) and 2). If that does not work, you'll have to hunt down the the FQDN which you need to redirect to 127.0.0.0 (not a typo, don't use 172.0.0.1).
4 - If you need a Free DDNS name, you'll have to find a provider then either install their own DDNS updater or use ddclient to update it.

I am sorry but this has nothing to do with IBM. Please remember that ClearOS6 was built directly off RedHat EL6 (at the time Centos was having internal problems). There is nothing in particular to stop a future ClearOS 8 or 9 being directly build from RedHat or its derivatives, AlmaLinux, Rocky or even Oracle Linux and moving between them is only a little more than changing source repos (perhaps not OracleLinux, but I don't know) and stripping out any branding. The issues with ClearOS (lack of) development are entirely internal.

There has been some support for a few issues, but not much - and he is on holiday for a week now. Completely wrong answers have been given and one system has potentially been bricked and then abandoned by support. It seems that the 4h and 24h response times contracted on Platinum and Gold systems respectively are not being honoured with tickets unanswered for over 2 weeks. Another Clearcenter service seems to have gone down on Friday and all its tickets are being ignored. I hear nothing from Michael so I doubt if I have any future left with Clearcenter. The whole thing is a sorry saga.

Re: Docker

That is ClearGLASS for you. Have a look in the webconfig.

Hello Herm. I've seen your tickets and feel very much for you. Unfortunately at the beginning of August, Clearcenter decided not use my services this month, but at the same time, don't seem to have made any arrangements for ClearOS technical tickets to be answered. Also there have been no updates to ClearOS as I do them but fortunately, there don't appear to have been any critical CVE patches released so at least ClearOS still appears to be secure.

I'm afraid I have no idea what is going on in Clearcenter. All I can do is suggest you e-mail Michael Proper directly at mproper@clearcenter.com.

I am really sorry I can't help as I can see you are desperate. For me, I am likewise in limbo

That is ClearGLASS for you. Have a look in the webconfig.

Is that a personal VPN or a ClearOS VPN? These days the proxy is only worth using in one of the non-transparent modes and that is quite an intrusive set up as all PC configs need adjusting. It is also quite resource intensive but the only way to filter https. I avoid it if I can.

Welcome to the forums.

Your issue sounds odd. Is it only https and not http? If it is both, is ClearOS in gateway mode? Are you using any filtering such as the Proxy/Content Filter or Gateway Management? In your IP Settings screen have you set each NIC to a separate subnet?

Re: TLS 1.2

So what is your website and what is the conf file in /etc/httpd/conf.d/ which drives it? Please post the contents?