Does i-MSCP should be always reachable, even if the engine is broken? 27
Yes (23) 85%
No (4) 15%
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.