Hi there.

I have working certyficate for my domain but when I'm trying get access to https://mydomain.com:2199/ Im getting SSL sertyficate error

"(net::ERR_SSL_PROTOCOL_ERROR)"

https://mydomain.com/ working perfectly

What could be wrong ??

Did you actually add nginx's SSL directives to the configuration file in etc/web.d/cc-interface.conf?  If so, please post what you've got and I'll be happy to take a look.

If not you're basically doing the equivalent of visiting https://www.google.com:80 -- eg: trying to access an HTTP server using the HTTPS protocol, in which case you're getting the expected (and correct) result.

Did you actually add nginx's SSL directives to the configuration file in etc/web.d/cc-interface.conf?  If so, please post what you've got and I'll be happy to take a look.

Could You explain me how to do this ?
I think I don't have nginx (not sure). I'm using Plesk panel for applying certs.

Enabling SSL requires adding the SSL directives to your web.d/cc-interface.conf file.  It's not a straightforward procedure so you can either check the nginx wiki at http://wiki.nginx.org/ or wait for the next build where we have a commandline utility to toggle SSL automatically.

After enabling ssl support by command line I'm getting this:

400 Bad Request

The plain HTTP request was sent to HTTPS port
cc-web/0.7.69

That means you're doing the opposite of what you were doing before... you're using http:// to access an SSL server instead of https://. Your URL scheme always needs to match the protocol being spoken by the server.

After executing command setssl I'm getting error

Starting Centova Cast: cc-control cc-appserver cc-web [emerg]: "ssl" parameter can be specified for the default "listen" directive only in /usr/local/centovacast/etc/web.d/cc-interface.conf:34
- failed
cc-control

After adding 'default' to listen line everything starting, but when type in https:// it's redirecting me automaticly to http:// ....

What I'm doing is:
1. Go to address https://maindomain.com:2199
2. It's redirecting me to http://maindomain.com:2199/login/index.php (I'm getting error 400 about plain HTTP)
3. I'm again typing in  https://mydomain.com:2199/login/index.php (WORKING, now I can login)
4.After loging in it redirecting me to http://mydomain.com:2199/admin/index.php ( again error 400)
5. Let's again change HTTP to HTTPS. Now redirected to http://mydomain.com:2199/admin/index.php?page=accounts
6. So let's try one more time change HTTP to HTTPS ....
AND.......

Hurrah !

I'm logged in and everythings works until I logout ;P

There is something wrong with redirections.

Sorry, I should have mentioned you'll need to reinstall v3 with the new build in order to take advantage of the new SSL settings.  It required a bunch of changes to the nginx configuration files (as I mentioned before it's not a straightforward procedure) and without reinstalling you won't have the new directives in your configuration files.

So I have to fully reinstall CentovaCast panel ?

Normal update is not enough ?

I've done update with '--force' option but there is still the same problem

Yes, in this case a full reinstallation is required if you want the SSL functionality.  Obviously if v3 were in production I would have put in the extra time to add a whole upgrade process for this, but the amount of effort involved just isn't worth it for the beta.

We're going to be advising everyone to replace their beta installations and reinstall fresh anyway when RC1 is released and we go to feature-freeze, so either way, a reinstallation is coming if you intend to transition to the stable release when it becomes available.