ISPConfig SSL certificate

With the address https://webserver.dominio.it:8080 it does not go, with the ip address yes.

 

Your url redirects to http://byzzpro.com/. The 8080 port does not work at all, probably because it redirect to that other site that does not listen on port 8080.
Something is wrong with your setup.
And like I suspected in two previous messages, your sertificate is for hostname *.dondominio.com. not the URL your ispconfig server uses.

 

No but the http://byzzpro.com/ has nothing to do with me the webserver.dominio.it was to understand but it is not the real address, at the post of the domain.it there is my real domain

 

Yes, the domain after webserver is mine.

 

No but that is not my domain it was one that I put to make it clear, the domain after webserver. it is a real domain that I registered myself.

 

ok so if I understand correctly this is why on the site it gives me the secure certificate while from the ip no, another thing so if I made public the host name of the server which is webserver.ilmiodominio.it the certificate would be just as safe as that of my site. If so, how can I make my server hostname public? Thanks

 

Ok, maybe I could have understood the problem that is that the certificate is not recognized as secure because I access ISPConfig from ip address and therefore it does not give me the certificate as safe as you told me, but if I were to access from the name of the https server : //webserver.ilmiodominio.it: 8080 should give me the certificate as safe if I don't get it wrong.
So if I can I ask another question as if I enter the name of the server eg. webserver.miodominio.it does not solve anything for me how should I make the name of the server public so that it is resolved with the public ip address? Thanks

 

is it webserver.ilmiodominio.it or webserver.miodominio.it?
both domains are registered. miodominio.it has ip 109.233.126.152 and a webserver subdomain A record pointing to the same ip.
ilmiodominio.it has the ip 167.86.80.223 and no A record for webserver in it's dns.
miodominio.it has no cert, or doesn't support tls1.2 or newer
ilmiodominio.it has a self-signed wildcard cert.

 

Those are not my domains are examples to understand.
In the real "configuration" what is after webserver. it is my real domain registered by me.

 

you've used at least 3 different domain names, and then said they're only examples.
perhaps if you stopped listing examples and gave the REAL domain names and subdomains, it would be a lot easier for us to help you troubleshoot it.

please don't say it's webserver.dominio.it, as that's a cname to hostingsrv12.dondominio.com

 

I didn't think you needed the real server name, I thought an explanation was enough for what I did the example.

 

We normally don't require them, but, sometimes when explanation are not clearing things and we keep circling without solving the real problems, providing further details may help.

 

Sorry I didn't specify that it was an example because I thought it was clear from the fact that I wrote mydomain.it

 

But so since I may have figured out what the problem is from your explanations, how do I make the server name public? Thanks

 

create an A record for it in your dns.

 

Ok now I try thanks, but will it work even if my dns are managed separately and not within ISPConfig? Thanks

 

yes. as long as your dns config is valid and accessible.