I have a dumb question about ispconfig.vhost

[Parsec]

The ISPC panel is accessed by using port 8080 and you can add a SSL cert for this to make it secure. So therefore it's supposed to work by going to (for example) https://server1.example.com:8080/

This is well and good but the ispconfig.vhost file for apache lists:
Listen 8080
NameVirtualHost *:8080
<VirtualHost _default_:8080>
..etc..etc..

What this means is if one adds a few clients and sites and lets say a clients site is www.somedomain.com then they can access the ISPC panel via https://www.somedomain.com:8080/ BUT because the SSL cert doesn't match it will throw up a warning.

Now I know you are going to say - tell your clients to login at https://server1.example.com:8080/ not by using their own domain...

My dumb question is:- Why is it this way? Wouldn't it be correct to specify the host or IP in ispconfig.vhost rather then having it at *:8080?

[kendel]

You can create your own host file and give it a ServerAlias example: panel.example.com
Default https:// should be port 443 (I believe), you can create your own host file using the details of ISPConfig host files (make a duplicate) then make the necessary changes to respond to https:// with no port. I did the same thing but with a proxy.

[Parsec]

I understand what you are saying, but that's just merely creating more apache confs for no real reason.
I am wondering why it's created like it is. In a perfect world I'd just adjust the current conf, but ISPC will overwrite it at every update.

[till]

I am wondering why it's created like it is.

It is created like this because it should work like it is currently implemented. This might be different from what you might want to have on your server off course but the current implementation works as it should.

[Parsec]

Originally Posted by till

It is created like this because it should work like it is currently implemented.

Maybe it should but it doesn't. It is throwing up SSL warning notices indicating the server is mis-configured.

This might be different from what you might want to have on your server off course but the current implementation works as it should.

It has nothing to do with what I want, the setup throws up an SSL error. That's got nothing to do with "what people want".