HTTPS possibilities (same domain, self signed cert, ...)

[dedeco]

Hello,

I am thinking about using HTTPS for a new page, and so I looked at the HTTPS resource here. It is paid (with altercents or not), so it hinders my initial ideas a bit.

I understand and imagine the HTTPS you offer, in a separate domain, is something that is worth the cost. It should have a signed certificate by a common authority (is this guess correct?), and everything else. But I just want to build my own certificate, self signed (usable, although me and all other users would get a warning for it, but does not matter initially).

Further, the HTTPS page is deactivated after a year if we can't build up enough altercents - and no alternative but paying would be left, by this time. And that possibility hinders it up even more to not choosing Altervista for this.

Is there a way to use https://myuser.altervista.org with a self signed certificate (which I could provide, so the server can be configured with it) instead of https://myuser.ssl.altervista.org ?

If not, is there any other possibility I don't know or did not think?

Ideas, suggestions, comments... everyone is welcome.

[karl94]

It should have a signed certificate by a common authority (is this guess correct?)

You can already check for yourself using the URL you wrote.

Is there a way to use https://myuser.altervista.org with a self signed certificate (which I could provide, so the server can be configured with it) instead of https://myuser.ssl.altervista.org ?

That is not possible, HTTPS support is only provided by using the service purchasable from the AlterVista control panel.