Posts by Nuxwin

    I have a custom billing system, and my online payment partner communicate with an old client with us...

    That client not support SNI, and apache get back 403 error message:

    [Tue Nov 06 08:39:05.759045 2018] [ssl:error] [pid 16618:tid 140185341699840] AH02033: No hostname was provided via SNI for a name based virtual host


    I already talked to them, but they need development in they system... Meantime I need solution for this...

    OK... The problem is that disabling SNI check in the vhost file that belongs to your billing system is not sufficient if that vhost is not seen as the default name-based vrtual host for the IP/PORT compound:


    Quote from apache documentation

    This directive sets whether a non-SNI client is allowed to access a name-based virtual host. If set to on in the default name-based virtual host, clients that are SNI unaware will not be allowed to access any virtual host, belonging to this particular IP / port combination. If set to on in any other virtual host, SNI unaware clients are not allowed to access this particular virtual host.


    So here, you have two choices:


    First choice

    Disable SNI vhost checking globally. This can be done through the /etc/apache2/mods-available/ssl.conf file.


    Second choice

    Assign a dedicated IP for the billing site, then make sure that the IP is only set (used) for the vhost of the billing system, then disable SNI vhost check in the billing vhost. This could involve the creation of an i-MSCP customer for the billing system subdomain only. Regarding the SNI directive, you can add it into the /etc/apache2/imscp/<domain.tld> file for persistence.

    symphosius


    Well, ifconfig show that the IP 84.200.83.93 is configured on the eth0 interface:


    Code
    1. eth0 Link encap:Ethernet Hardware Adresse 4c:cc:6a:89:03:a6
    2. inet Adresse:84.200.83.93 Bcast:84.200.83.255 Maske:255.255.255.0
    3. inet6-Adresse: fe80::4ecc:6aff:fe89:3a6/64 Gültigkeitsbereich:Verbindung
    4. UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
    5. RX-Pakete:7343336 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
    6. TX-Pakete:110085 Fehler:0 Verloren:0 Überläufe:0 Träger:0
    7. Kollisionen:0 Sendewarteschlangenlänge:1000
    8. RX-Bytes:496522860 (496.5 MB) TX-Bytes:10613929 (10.6 MB)


    I presume that it's the primary server IP. The problem is that in your /etc/network/interfaces file, that IP is not configured manually, and so, i-MSCP add a configuration stanza for it on an alias interface eth0:1001:


    Code
    1. # i-MSCP [84.200.83.93] entry BEGIN
    2. auto eth0:1001
    3. iface eth0:1001 inet static
    4. address 84.200.83.93
    5. netmask 24
    6. # i-MSCP [84.200.83.93] entry ENDING


    Of course, because the IP is already configured on the eth0 interface, this cannot work... Basically, you need to remove the above configuration stanza from your /etc/network/interfaces file and configure the IP manually. A stanza such as:


    Code
    1. auto eth0
    2. iface eth0 inet static
    3. address 84.200.83.93
    4. netmask 255.255.255.0
    5. broadcast 84.200.83.255
    6. gateway <your_gateway>


    should be OK. Don't forget to replace <your_gateway> by your gateway. Once done, retry the upgrade.

    Dear community,


    Our own Debian/Ubuntu APT repositories will be soon availables.


    Our site https://deb.imscp.org/ is already online but the repositories are not yet pushed on our production network.


    At first, we will provide packages for the PhpSwitcher plugin but in near future, we will also provide packaged version of i-MSCP, including plugins.


    Feel free to subscribe to https://twitter.com/debimscporg that is the place where most important changes and news are published regarding our repositories.