Posts by jackstone

    Hey tracer thanks for your reply!


    # netstat -luntep|grep 443

    tcp 0 0 *:8443* LISTEN 0 4031892 18077/nginx: master

    tcp6 0 0 :::443 :::* LISTEN 0 4091968 4142/apache2

    tcp6 0 0 :::8443 :::* LISTEN 0 4031893 18077/nginx: master

    And SSL Labs says :


    Assessment failed: No secure protocols supported

    It is very weird, I have another server with the exact same configuration, i checked each file in /etc/apache2 , i checked enable modules of apache, they are identical, on one server everything works fine, and this one it doesn't. I even checked apache2 related installed packages, same version and same packages installed on both servers, I'm really lost, no idea where to look next :/

    A more verbose curl.

    Ok so, after the upgrade from Ubuntu 16.04 to Ubuntu 18.04, I reinstalled i-MSCP and now the panel (or anything else) doesn't work on apache 443, before the upgrade I had the PanelRedirect plugin installed which would enable customers to access the panel on a normal URL without :8443 at the end, now the panel works properly if I add :8443 at the end, but on the normal URL Chrome gives the following error :

    1. This site can’t provide a secure connection website sent an invalid response.
    2. Try running Windows Network Diagnostics.

    If I try to curl https://localhost I get this : (If I try to curl any https site which is NOT on this server, it works fine)

    1. # curl -I https://localhost
    2. curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

    I checked all Apache modules, I check OpenSSL version, everything *seems* fine, I also compared settings between this server and another recently updated server which works fine and couldn't find any difference in configs.

    The only thing I can think of is that i-MSCP was recently upgraded from a very old version (1.1.21) to the latest 1.5.3-2018 and maybe some old config file was left behind which is interfering with Apache. I tried to run the installer again with --reconfigure and nothing changed.

    The only logs I get in Apache are :

    Quote - - [09/Feb/2019:14:15:12 +0200] "\x16\x03\x01\x02" 400 226 "-" "-" - - [09/Feb/2019:14:15:19 +0200] "\x16\x03\x01\x02" 400 226 "-" "-" - - [09/Feb/2019:14:15:25 +0200] "\x16\x03\x01\x02" 400 226 "-" "-"

    It's like Apache doesn't know anymore how to handle a SSL connection.

    ANY IDEAS ?! :idea:

    Ubuntu 18.04 - i-MSCP 1.5.3 Build: 2018120800

    P.S. When I finished the reconfigure of the panel after it said I can login into the panel the following error appeared below for 3 different sites :

    [ERROR] Servers::named::bind::_compileZone: Couldn't compile the zone: Unknown error

    Thank you for your reply Nuxwin but Bulli managed to help me out before you posted the reply, big thanks to him for the support.


    Please next time, ask us before doing anything... Asking us after playing with something you don't understand is not really the right way. A customer that is processing such way would lose free support.

    You have to understand that I didn't have much choices, it is a production server which could only be upgraded during the night because during the day there is intense traffic. So when I updated from Ubuntu 16.04 to 18.04, rebooted, ran the imscp-autoinstall with the same version which was installed on 16.04 and the installer would quit spitting errors I panicked, the server cannot be offline for a very long period of time and services must be running, with the installer failing and everything offline at 2 AM I didn't have much choice but to try to fix the errors which were displayed in the setup dialog in order to successfully install i-MSCP and resume the services, thinking that after everything is running I can correct the errors manually. I don't see any other way I could have played this. I'm not really sure what the exact problem was, Bulli knows better, he fixed it, but I suspect something went wrong with the secondary IP of the server during the upgrade, which I also had to remove manually from the sql database before being able to successfully install i-MSCP, but by removing the IP manually after your reply I realize that most likely that was the cause why the subdomains kept failing and giving the error because they were assigned to the secondary IP and the secondary IP was deleted. At least now I have a better understanding of some things. :rolleyes:

    Hello everyone,

    I'm having trouble after a recent upgrade from Ubuntu 16.04 to Ubuntu 18.04, after the upgrade I re-ran the i-MSCP installer and it wouldn't install giving out an error about Data not found for subdomain, so I manually deleted the conflicting subdomains from the mysql database thinking that after a successful install I can just re-add them back, the problem is that now they are stuck in Addition in progress... and when i try to run perl /var/www/imscp/engine/imscp-rqst-mngr -v it gives out the following error :

    1. [FATAL] iMSCP::DbTasksProcessor::_processModuleDbTasks: Modules::Subdomain::_loadData: Data not found for subdomain (ID 4) at /var/www/imscp/engine/PerlLib/Modules/ line 156, <$fh> line 408.
    2. ...propagated at /var/www/imscp/engine/PerlLib/iMSCP/ line 496, <$fh> line 408.

    I tried to edit the database and change de subdomain status from toadd to -> ok, now the addition in progress disappeared but the subdomains still don't work, when I try to dig @localhost they won't resolve.

    Any ideas how to fix this ?!

    Forgot to mention, i-MSCP version 1.5.3 Build: 2018120800 running on Ubuntu 18.04

    Tried both ways, but by deleting /var/www/imscp i found out that in most cases the installer progresses much further before it spits out an error, if I leave the original /var/www/imscp i get maybe 4-5 steps before it crashes, if i delete it i go 10-11 steps :D