Infrastructure Update: MidiAndMore.Net Migrates Web Server to Apache and Optimizes Configuration
MidiAndMore.Net has successfully transitioned its core web server and reverse proxy infrastructure from NGINX to Apache, resolving several legacy configuration issues to boost platform stability.
Dear MidiAndMore.Net Community,\r\nWe want to inform you about an important infrastructure upgrade completed during our recent maintenance window. To better support our growing platform requirements, we have officially migrated our web server and reverse proxy layer from NGINX to Apache HTTP Server.\r\n\r\nWhy this change?\r\nWhile NGINX has served us well, Apache provides our backend with enhanced flexibility. This includes superior dynamic module management and robust directory-level configurations, allowing us to deploy future platform updates more efficiently.\r\n\r\nBug Fixes and Optimizations:\r\nDuring the migration process, we performed a thorough audit of our routing and security setup. We successfully identified and resolved several long-standing configuration errors:\r\n\r\n
- \r\n
- Fixed a misconfigured SSL/TLS cipher suite that caused intermittent handshake failures on older browsers.\r\n
- Resolved an upstream timeout error that occasionally dropped active WebSocket connections.\r\n
- Optimized rewrite rules to eliminate redundant internal redirects, reducing overall server load.\r\n
- Corrected header permissions to strengthen our cross-origin resource sharing (CORS) security policy.\r\n
Replies
Login to start a thread or reply. Guests can read only.