MaxWebServer ETA and further inquiries.

Issue 

• Is there an EasyApache configuration recommendation for using with MAx?
• How would one best confirm that MAx is properly running?
• For systems previously using NGINX through cPanel, what sort of changes does this new config have with the NGINX Manager within WHM/cPanel? 
• If EasyApache updates are needed for say php changes, is there a process to rebuild MAx that needs to be followed?
• I saw in the documentation that apache config shouldn't be changed, but wouldn't we need to configure this for the fallback option of apache if max is disabled on a site?
• In theory, if we only plan on offering MAx as an option, can we remove apache completely?
• How does the MultiPHP Manager interact with MAx? We previously used PHP-FPM with our NGINX setup, and php handler has always been set to cgi; is this correct? 

Solution

When is the full release of MAx Web Server expected?

We are planning a release in Q4 2026.
 
 

Is there an EasyApache configuration recommendation for using with MAx?

There is no specific recommendation, but for PHP processing required handler is either PHP-FPM or LSAPI.
 
 

How would one best confirm that MAx is properly running?

Either apache2nginx state to see it's operational and additoinally apache2nginx list-proxied to reveal a list of websites that failed to convert and are currently handled by Apache.
 
 

For systems previously using NGINX through cPanel, what sort of changes does this new config have with the NGINX Manager within WHM/cPanel?

For pre-existing systems with NGINX, things depend on whether NGINX cache was enabled.
If cache was enabled, switching to MAx Web Server retains cache enablement and NGINX stays in proxy mode.
If cache was not enabled, switching to MAx Web Server, NGINX serves websites directly where MAx Web Server is able to convert Apache config files.
 
 

If EasyApache updates are needed for say php changes, is there a process to rebuild MAx that needs to be followed?

There's no process to follow, everything should be handled automatically.
 
 

I saw in the documentation that apache config shouldn't be changed, but wouldn't we need to configure this for the fallback option of apache if max is disabled on a site?

Editing global Apache configuration will lead to rebuild of entire NGINX configuration, while editing single .htaccess files is normal, MAx Web Server handles their configuration to NGINX configuration seemlessly.
 
 

In theory, if we only plan on offering MAx as an option, can we remove apache completely?

This is a planned feature, to disable/remove Apache completely, once MAx Web Server fully understands Apache syntax.
 
 

How does the MultiPHP Manager interact with MAx? We previously used PHP-FPM with our NGINX setup, and php handler has always been set to cgi; is this correct?

CGI is not supported by NGINX, so upon switch to MAx Web Server, you're offered to switch to either LSAPI or PHP-FPM.