Category Archives:

500 error in Mono + Apache + ASP.NET

There is ASPX(C#) that was running on IIS. I want to operate this on Mono.

We were able to build the environment and check the operation on xsp4. However, it does not work on Apache.(500 error) Likewise, the URL parameter (http:///Layer/sample.aspx?app=sampleApp) also does not work.

I think that the setting of Apache is bad, but I want advice because I do not know where it is wrong.


CentOS Linux release 7.4.1708 (Core)

$ mono -V

Mono JIT compiler version (tarball Tue May  8 09:28:02 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors.
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none
        Misc:          softdebug
        Interpreter:   yes
        LLVM:          supported, not enabled.
        GC:            sgen (concurrent by default)

$ httpd -v

Server version: Apache/2.4.6 (CentOS)
Server built:   Apr 20 2018 18:10:38


# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:> for detailed information.
# In particular, see 
# <URL:>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
ServerRoot "/etc/httpd"

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
Listen 80

# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/
Include conf.modules.d/*.conf

# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User apache
Group apache

# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.

# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. [email protected]
ServerAdmin [email protected]

# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
ServerName <hostname>:80

# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other 
# <Directory> blocks below.
<Directory />
    AllowOverride none
    Require all denied

# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.

# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/var/www"

# Relax access to content within /var/www.
<Directory "/var/www">
    AllowOverride None
    # Allow open access:
    Require all granted

# Further relax access to the default document root:
<Directory "/var/www/html">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important.  Please see
    # for more information.
    Options Indexes FollowSymLinks

    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    AllowOverride None

    # Controls who can get stuff from this server.
    Require all granted

# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
    DirectoryIndex index.html

# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
<Files ".ht*">
    Require all denied

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "logs/error_log"

# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

<IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #CustomLog "logs/access_log" common

    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    CustomLog "logs/access_log" combined

<IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo

    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"


# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted

<IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig /etc/mime.types

    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml

# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the 
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    MIMEMagicFile conf/magic

# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/"
#ErrorDocument 402

# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#EnableMMAP off
EnableSendfile on

# Supplemental configuration
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf

Include /etc/httpd/conf.d/mod_mono.conf


# mod_mono.conf

# Achtung! This file may be overwritten
# Use 'include mod_mono.conf' from other configuration file
# to load mod_mono module.

<IfModule !mod_mono.c>
    LoadModule mono_module /usr/lib64/httpd/modules/

<IfModule mod_headers.c>
    Header set X-Powered-By "Mono"

AddType application/x-asp-net .aspx
AddType application/x-asp-net .asmx
AddType application/x-asp-net .ashx
AddType application/x-asp-net .asax
AddType application/x-asp-net .ascx
AddType application/x-asp-net .soap
AddType application/x-asp-net .rem
AddType application/x-asp-net .axd
AddType application/x-asp-net .cs
AddType application/x-asp-net .vb
AddType application/x-asp-net .master
AddType application/x-asp-net .sitemap
AddType application/x-asp-net .resources
AddType application/x-asp-net .skin
AddType application/x-asp-net .browser
AddType application/x-asp-net .webinfo
AddType application/x-asp-net .resx
AddType application/x-asp-net .licx
AddType application/x-asp-net .csproj
AddType application/x-asp-net .vbproj
AddType application/x-asp-net .config
AddType application/x-asp-net .Config
AddType application/x-asp-net .dll
DirectoryIndex index.aspx
DirectoryIndex Default.aspx
DirectoryIndex default.aspx

# add setting
MonoAutoApplication disabled

AddMonoApplications monoapp "/Layer:/var/www/Layer"
MonoServerPath monoapp "/usr/bin/mod-mono-server4"
<Location /Layer>
    SetHandler mono
    MonoSetServerAlias monoapp
<Directory "/var/www/Layer">
AllowOverride None
Require all granted

All files Permission: 755
Both users and groups: apache

Host ASP.Net C# website to Apache or weblogic

We have a Asp.Net website code behind C# framework 4.0 hosted on IIS 6.2. Now we have been asked to migrate it to either Apache or weblogic server. My question is where can we host our website where minimal changes are needed to host our website. And based on your experience do we need to do any code changes in our web site to make it compatible with Apache or Web logic server. Kindly suggest where should we migrate so that minimal or no code changes needed. and minimal efforts for hosting.

how to redirect url with it’s url parameters to custom page in

I have one default page as : http://localhost:9909/shrtn.aspx

I have added a rule in web.config (default web page rule) using which if i enters http://localhost:9909/ it redirects to http://localhost:9909/shrtn.aspx

rule is as follows :

          <add value="shrtn.aspx" />

But If enter http://localhost:9909/abcdef it throws 404 error page. Is there any way by which i can redirect following url : http://localhost:9909/abcdef to http://localhost:9909/shrtn.aspx

Also i need to transfer parameters, i.e. if i hit url : http://localhost:9909/abcdef , it should redirect to http://localhost:9909/shrtn.aspx?abcdef.

is there any way to implement this??

Rename product page with web.config

Since I have this URL:

What is the better approach to rewrite this URL like this:

With IIS I was able to generate this URL

This is the web.config code:

<rule name="RedirecionaPagProduto" stopProcessing="true">
    <match url="^exibe_produtos\.asp$" />
        <add input="{REQUEST_METHOD}" pattern="^POST$" negate="true" />
        <add input="{QUERY_STRING}" pattern="^produto=([^=&amp;]+)&amp;cor=([^=&amp;]+)&amp;url=([^=&amp;]+)$" />
    <action type="Redirect" url="{C:1}/{C:2}/{C:3}" appendQueryString="false" />
<rule name="RenamePagProduto" stopProcessing="true">
    <match url="^([^/]+)/([^/]+)/([^/]+)/?$" />
        <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
        <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
    <action type="Rewrite" url="exibe_produtos.asp?produto={R:1}&amp;cor={R:2}&amp;url={R:2}" />

Anyone can help?

301 Permanent Redirection, Urls are not changing

I am implementing 301 redirection, but the problem that I am facing is, the urls are not changing, and when I implements 302 url start changing, is their any way through which I will implement 301 and the urls will change as per the need.

Like: and I need only one URL to display in my browser when I hit anyone of the above mentioned URLs.

Thank you!!

Apache2 ASP MVC Razor view crashes when referencing PCL enum for dropdown

I am new to using on ubuntu with mono, I have several websites working very well indeed using MVC5, though I recently migrated a project over and have found that forms referencing enums from a referenced PCL cause views to crash. Below is my EnumDropDownList call which works fine on a windows host.

<div class="form-group">
@Html.LabelFor(m => m.Type, new { @class = "control-label" })
@Html.EnumDropDownListFor(m => m.Type, new { @class = "form-control" })

When viewing this in the browser on the ubuntu host however I get the following error

The view found at '~/Views/portal/productgroup.cshtml' was not created.

Additional the stack trace is

     at System.Web.Mvc.BuildManagerCompiledView.Render (System.Web.Mvc.ViewContext viewContext, System.IO.TextWriter writer) [0x00061] in <cc73190bab9d435c831510ff295c572a>:0 
  at System.Web.Mvc.ViewResultBase.ExecuteResult (System.Web.Mvc.ControllerContext context) [0x00080] in <cc73190bab9d435c831510ff295c572a>:0 
  at System.Web.Mvc.ControllerActionInvoker.InvokeActionResult (System.Web.Mvc.ControllerContext controllerContext, System.Web.Mvc.ActionResult actionResult) [0x00000] in <cc73190bab9d435c831510ff295c572a>:0 
  at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive (System.Collections.Generic.IList`1[T] filters, System.Int32 filterIndex, System.Web.Mvc.ResultExecutingContext preContext, System.Web.Mvc.ControllerContext controllerContext, System.Web.Mvc.ActionResult actionResult) [0x0000b] in <cc73190bab9d435c831510ff295c572a>:0 
  at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive (System.Collections.Generic.IList`1[T] filters, System.Int32 filterIndex, System.Web.Mvc.ResultExecutingContext preContext, System.Web.Mvc.ControllerContext controllerContext, System.Web.Mvc.ActionResult actionResult) [0x0004f] in <cc73190bab9d435c831510ff295c572a>:0 

Is there a way I need to reference the external assembly in my controller or my razor view? Is this a common issue or could there be something specific going on?

For reference the PCL holds some shared code for use between my site and a mobile app built using Xamarin. The PCL has the profile .NET framework 4.5 in addition to all of the Xamarin ones etc. The code is fully operational on windows and will work if I remove references to the enum stored in the PCL.

Any help would be greatly appreciated.

Mono Asp.Net Can’t Resolve HTTP 500. Error processing request

Using C# (framework 4.0) and Sqlite3 Database created Web Application and run in my hardware with Linux Ubuntu Platform (Mono - and Apache server.

It run correctly most of the time but sometime web got crash and gives error as below.

enter image description here

First, It Load Login.aspx Page but After click on LogIn Button it will gives above error. and after apache restart it run correctly.

Note: I think Login.aspx load from cache memory.

I am just not getting why web got crash many time.

Got "Apache/2.2.22 Server at Port 80" when trying to go to local website that is on IIS

I am running window 10. I had website that was successfully publish on local IIS. When I go the to the site, I get this error. I looked every for Apache on the machine. I didn't see it. I don't remember install it.

Not Found The requested URL /websiteName was not found on this server. Apache/2.2.22 Server at Port 80

I notice that the URL has takes me to

How do I solve this problem?

Any help is much appreciated. server redirect causing Not Found [CFN #0005]

So I've built a very small form website using and visual studio express 2015. The site works fine locally so far - but when I push everything to the hosted site it doesn't work.

The issue I currently have is the page is redirecting to a non-file extension page which results in the Not Found [CFN #0005] error message. So when going to in the browser it is redirecting to - and since there is no file named just 'mainpage' it is returning the not found error.

I've looked in a lot of places to try to find out why this is an issue - are there rewrite rules to put in web.config? Nothing seems to have worked. Should there be entries in the .htaccess file? Does there need to be some kind of configuration change on the server - which would require the hosting company to make? (by the way, the hosting company is saying its strictly a code issue and won't help).