1

Topic: switching to apache2 - what will break?

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: debian 9
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
A quick question:

iRedMail no longer installs with apache2 , only nginx is supported apparently.  I need to switch to apache2 because nginx will not serve any css to other sites I set up on the server. There seem to be many, many different reasons why this can happen with nginx, but nothing I have found after two days of searching solves the problem.  If the main mail parts will still run with apache2 on the server, I may be able to manage without some web functions that are supported by nginx.   

So I would like to know which parts of iRedMail will break as a result of installing apache2.

TIA

2

Re: switching to apache2 - what will break?

artavec wrote:

because nginx will not serve any css to other sites I set up on the server.

This doesn't make any sense, Nginx should work fine in this case. Did you get any error message of this issue?

----

Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee

3

Re: switching to apache2 - what will break?

ZhangHuangbin wrote:
artavec wrote:

because nginx will not serve any css to other sites I set up on the server.

This doesn't make any sense, Nginx should work fine in this case. Did you get any error message of this issue?

Bizarrely no error messages, and nothing at all logged that I could find. All css was just silently dropped.  I thought the firewall might be blocking it somehow, but that did not make sense as it would go via the same port. 

Never mind, I lost patience and transferred all the http activity to another cloud server, which I coincidentally had recently reimaged and set up with nginx.  It works fine there, so I will let the two servers remain specialist, one for mail and one for 3w.

It has to be something I misconfigured, but sometimes life is too short to solve all the silly problems...

4

Re: switching to apache2 - what will break?

artavec wrote:

Bizarrely no error messages, and nothing at all logged that I could find. All css was just silently dropped.  I thought the firewall might be blocking it somehow, but that did not make sense as it would go via the same port. 

- Does your web browser report "404 not found" error for these CSS files?
- Does Nginx log these "404 not found" error in its log file when you access the website? If no, then probably your firewall or some network device blocks the requests and it doesn't reach Nginx at all. In this case, no matter Apache/Nginx you use, you get same issue.

----

Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee