[Mono-aspnet-list] mod_mono fails: HTTP 503, no error log

Yves Goergen nospam.list at unclassified.de
Fri Dec 12 15:08:14 UTC 2014

Am 12.12.2014 um 14:43 schrieb miniBill:
> Do you need to use apache+mod_mono or are you open to considering nginx
> + fastcgi-mono-server?

Yes, Apache web server is a requirement. It's already running and using 
ports 80 and 443 and handling virtual domains with optionally SSL. 
Anything programmable must integrate into that, otherwise I can't use it.

I've asked about Apache + FastCGI before, but I was recommended to try 
mod_mono instead. My main concern was that mod_mono would execute the 
mono engine inside the apache process, just like mod_php works, but that 
seems false and the graphics on the mod_mono documentation page suggest 
that each mono server process (which can host multiple AppDomains) can 
be run under a different system user account. Since mod_mono is the only 
configuration documented for Apache, I've now tried that. But it doesn't 
seem to work.

If somebody can explain me how to set things up with FastCGI, including 
multi-user support, please reply in my other thread so I can try it.

Meanwhile, I've searched for external Windows-based ASP.NET hosting 
offers, but there are only very few, at least in my region, and they're 
too expensive for my needs. So .NET web applications continue to exist 
only on the inside of corporate firewalls (which is where I made them 
for up to now), not in the public web.

Yves Goergen

More information about the Mono-aspnet-list mailing list