Enhancement - The control panel must always be reachable using a specific HTTPD instance

  • Does i-MSCP should be always reachable, even if the engine is broken? 27

    1. Yes (23) 85%
    2. No (4) 15%

    [hr]
    Dear community ;


    We can enhance i-MSCP a bit by making it reachable on a different port using nginx. This can allow to mitigate the following issues:

    • The control panel will no longer be reachable on the default port 80/443 (by default)
    • Even if the engine is broken at some points (eg. if Apache is unable to restart), the control panel will always be reachable, meaning that the users will be able to see what's wrong via the control panel.


    You can give your opinion by participating to the related poll.


    Be warned: Here, We are talking only about the control panel (i-MSCP). It's useless to talk about nginx as frontal and so on because it's not the subject of this thread. Any post which deviate will be removed


    Thank you for your participation.


    Refs

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • @pdias


    Running i-MSCP on a standalone httpd instance is really cheap and this could be a great enhancement because this would allow to perform some maintenance tasks via the control panel such as forcing restart of Apache instance and so on...


    The memory footprint for NGINX, compared to Apache, is very low and this can also allow further things in future. Also, nginx is available in official Debian/Ubuntu repositories while the monkey server (as far I know) is not.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • That's a great idea!
    I've been thinking about what could be done during the upgrade.


    If i-MSCP runs on standalone httpd instance, we can do a firewall redirect tcp/80 and tcp/443 to admin ports during the upgrade, which displays a maintenance page.

  • @Nuxwin


    According to the monkey project website :

    Quote

    Monkey is already part of Debian and Ubuntu projects, but the packages available are always in very old versions.


    Monkey is already part of Debian and Ubuntu projects, but the packages available are always in very old versions.


    But if I remember well the old version (the one present in debian/ubuntu repos) does not provide fastcgi - php compatibility.
    So they provide their own repos


    I agree with You, nginx is an excellent choice,


    Regard's
    Paul

  • @Nuxwin


    Quote

    Be warned: Here, We are talking only about the control panel
    (i-MSCP). It's useless to talk about nginx as frontal and so on because
    it's not the subject of this thread. Any post which deviate will be
    removed


    Ok, I see but if i-MSCP use the Nginx for standalone httpd then later it can't be alternative of Apache.
    Maybe the lighttpd is better for standalone admin panel. In this case the Nginx can't be used for main webserver instead of Apache.

  • @jonci

    This does not prevent anything (eg, later we will still be able to use nginx as frontal for apache (eg, for static content)) ;) Don't worry ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • @MyIgel


    The goal here is to make the control panel reachable even if Apache is failing to restart.


    Therefore

    • We cannot listen to the default ports 80/443 using NGINX because those ports will be already used by Apache
    • We cannot use the proxy feature from apache to redirect the control panel traffic on port 80/443 to nginx because if Apache is down, the control panel will no longer be reachable.


    Of course, If you have a dedicated IP, it's still possible but we cannot handle all cases. Anyway, most of the control panels are not reachable through the default ports (80/443) for safety reasons.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206