Hello,
https:// noexistentsub ==> X, where X is an existent customer site, is the expected behavior without the ServerDefaultPage plugin. Now if you get the same behavior with the serverDefaultPage plugin, there is a problem
Hello,
https:// noexistentsub ==> X, where X is an existent customer site, is the expected behavior without the ServerDefaultPage plugin. Now if you get the same behavior with the serverDefaultPage plugin, there is a problem
Hi,
@Ninos when you are online, please let me know so i send you the TV-data that you can show.
@Nuxwin is it the expected behavior that https://noexistentsub.domainA.tld OR https:// noexistentsub.domainB.tld (different customer) OR https:// noexistentsub.domainC.tld (different customer) end up at the last added customer?
Yes with ServerDefaultPage i have the same behavior as without it, but all is in standart configuration in jessie , imscp and plugins.
Thanks
Yes, this is the default Apache behavior. When a host is not found, Apache serves the primary vhost (the first vhost found (loaded first)). The ServerDefaultPage plugin normally define two default vhosts, one for http and one for https, by configuring them in such way that they are always loaded first.
Question:
Do you have enabled SSL for the i-MSCP panel during setup? Please give us the result of the following command:
I see like a bug in the DefaultServerPage plugin. According https://github.com/i-MSCP/plug…ServerDefaultPage.pm#L123 you create the default vhost file for SSL only if SSL is enabled for the panel. The problem is that SSL for the panel (which is run via nginx) has nothing to do with SSL for customer's sites... The customer sites can have SSL enabled even if SSL is disabled for the panel. You should not rely on the PANEL_SSL_ENABLED parameter. This is surely the problem... We shoud talk about a way to solve that. The first idea would be to generate a dedicated SSL certificate for the default SSL vhost but the problem is that the certificate will not match the unknown hosts. An alternative would be to redirect from default SSL vhost to no-SSL default vhost. At least there should be an option for either, use a self-signed certificate (or one provided certificate through plugin configuration settings), or redirect on the default no-SSL vhost.
Thanks for your reply.
Here is the output of your command:
So the SSL for the Panel is not enabled during installation.
Addition:
Yes i see now that there is maybe a bug in the ServerDefaultPage.pm the vHosts don't get created on my system because PANEL_SSL_ENABLED = no
Thanks. Read my previous answer to understand why default vhost doesn't work with SSL. For now, You could simply enable SSL for the panel with a self-signed certificate and reinstall the ServerDefaultPage plugin once done.
You can enable SSL for the panel by running the following command and by answering the questions:
According the @AlpineSwiss answer, I can say that the problem comes from the ServerDefaultPage plugin that don't create the default SSL vhost when SSL is disabled for the panel.
@Nuxwin yes now i understand the behavior why this occurs.
The solution is now to activate SSL for the panel (but because i dont really need it, I will wait a fix for ServerDefaultPage)
Thanks guys.
EDIT: @Nuxwin Ok i have see your edit, I will give them a try later.
Other question, it is possible/allowed to insert some custom php-files (script) into the default-folder of the ServerDefaultPage ?
No, sorry. at this moment, there is not PHP handler set for the default vhost. That could be a feature request