Dual Madsonic servers?

Need help? Post your questions here.
gurutech
Contributor
Contributor
Posts: 323
Joined: 02 Jan 2013, 04:56
Has thanked: 11 times
Been thanked: 105 times

Dual Madsonic servers?

Unread post by gurutech »

I think this would be possible, to have two separate servers running on the same network, both on port 4040 (default), but accessible over the internet via a single domain name, followed by a different port number.

I have something similar set up on my router, where I can (for example) put in my domain.com:12345 to get to my website on one computer, and domain.com:54321 to get to another website on another computer, where they are running on port 80 on both computers.

I'm thinking if I can set up port 4040 to go to my main Madsonic server, and forward port 4041 to my secondary/test Madsonic server on port 4040, it should work, correct?

Another question I have is with the Android app, if I leave out the password on the server configuration, will it prompt me for the password each time I connect to that server, or will it only ask once and then just save it?
chali
Contributor
Contributor
Posts: 100
Joined: 13 Dec 2012, 16:25
Has thanked: 18 times
Been thanked: 35 times

Re: Dual Madsonic servers?

Unread post by chali »

gurutech wrote:I think this would be possible, to have two separate servers running on the same network, both on port 4040 (default), but accessible over the internet via a single domain name, followed by a different port number.

I have something similar set up on my router, where I can (for example) put in my domain.com:12345 to get to my website on one computer, and domain.com:54321 to get to another website on another computer, where they are running on port 80 on both computers.

I'm thinking if I can set up port 4040 to go to my main Madsonic server, and forward port 4041 to my secondary/test Madsonic server on port 4040, it should work, correct?

Another question I have is with the Android app, if I leave out the password on the server configuration, will it prompt me for the password each time I connect to that server, or will it only ask once and then just save it?
Hi

nah you probably have it set so that one goes to port 80 and the other goes to port 8080 or du you use https on one then it is 443 it uses. you can not be on the same ip to the same router and use the same port.

However, you can point on one, so one domain uses a different port.
or do you mean that you want to load balance between the server?


/ Chali
These users thanked the author chali for the post:
Madsonic
Rating: 7.69%
GJ51
Contributor
Contributor
Posts: 192
Joined: 15 Dec 2012, 17:52
Has thanked: 42 times
Been thanked: 83 times

Re: Dual Madsonic servers?

Unread post by GJ51 »

I have several sites on my network.

I just use a different port number and forwarding rule for each site.

For simplicity I associate the port number with the ip address so it's easy to remember which port goes with each ip address.

192.168.1.240:4040
192.168.1.241:4041

etc.

If I want to add ssl I just do the same thing,

192.168.1.240:440
192.168.1.241:441

I never use 80 or 443 just to avoid conflicts with other applications that want to use those ports.
These users thanked the author GJ51 for the post:
Madsonic
Rating: 7.69%
User avatar
Madsonic
Administrator
Administrator
Posts: 984
Joined: 07 Dec 2012, 03:58
Answers: 7
Has thanked: 1201 times
Been thanked: 470 times

Re: Dual Madsonic servers?

Unread post by Madsonic »

Hi there,

Network

... as addition to gary i recommend you, generally don't use port numbers below 1024

Info: http://www.staldal.nu/tech/2007/10/31/w ... elow-1024/


Multi-Instance

and don't forget: for each instance a different path for the database must be used! (if used on one Server)

gurutech wrote:I think this would be possible, to have two separate servers running on the same network, both on port 4040 (default), but accessible over the internet via a single domain name, followed by a different port number.

I have something similar set up on my router, where I can (for example) put in my domain.com:12345 to get to my website on one computer, and domain.com:54321 to get to another website on another computer, where they are running on port 80 on both computers.

I'm thinking if I can set up port 4040 to go to my main Madsonic server, and forward port 4041 to my secondary/test Madsonic server on port 4040, it should work, correct?
yes it work! :D

Example

Local Server:

Code: Select all

10.0.0.100:8001 --> ----- |         | --> 12.142.62.10:80
10.0.0.100:8002 --> ----- |  ROUTER | --> 12.142.62.10:81
10.0.0.110:8003 --> ----- |         | --> 12.142.62.10:82
10.0.0.110:8004 --> ----- |         | --> 12.142.62.10:83
gurutech wrote: Another question I have is with the Android app, if I leave out the password on the server configuration, will it prompt me for the password each time I connect to that server, or will it only ask once and then just save it?
that will not work. It will only work if you save the password to your settings.


best regards
gurutech
Contributor
Contributor
Posts: 323
Joined: 02 Jan 2013, 04:56
Has thanked: 11 times
Been thanked: 105 times

Re: Dual Madsonic servers?

Unread post by gurutech »

I guess I didn't explain myself too well in my original post... but you guys are pretty much confirming what I am trying to do.

I have one IP address (assigned via DHCP by my ISP), and use No-IP to provide a domain name. Within No-IP, I can have up to 3 "hosts" (using free version), so I have "gurutech1.no-ip.com", "gurutech2.no-ip.com", and "gurutech3.no-ip.com", each has a "web redirect" from port 80 to a different port, which I have one going to 4040 for Madsonic. The others I'm planning on going to 4041 and 4042.

On my firewall/router, I can take any port number (for example, 4041) as the "external" port number, and route it internally to any computer on my network, on ANY "internal" port. So what I have now is simply to forward 4040 to 4040, but I can also take external ports 4041 and 4042 and route them internally to port 4040 on different servers. (I have something similar set up so I can FTP to two of my computers using the same public IP address, and different port numbers, but leaving the FTP service running on port 21.)
These users thanked the author gurutech for the post:
Madsonic
Rating: 7.69%
bwood
Posts: 5
Joined: 10 Feb 2013, 07:09
Has thanked: 1 time
Been thanked: 3 times

Re: Dual Madsonic servers?

Unread post by bwood »

There is a somewhat more flexible way to do this using a reverse proxy. It requires a "server" running Apache (XAMPP) is a good way to get a working Apache setup for Windows) - http://www.apachefriends.org/en/xampp.html.

The advantage of this is that you can use a "standard" port (e.g. 80) to host the server. This allows access from networks where the administrator blocks URLs with an explicit port number (e.g. most corporate networks..). You can set up your no-ip DNS entries to point all sub-domains to your dynamic IP. An example DNS entry might be:

Code: Select all

$TTL 120
$ORIGIN example.com.
@ IN SOA ns1.no-ip.com. admin.no-ip.com. (2011112100 3600 300 1209600 120)
                                 IN NS     ns1.no-ip.com.
                                 IN NS     ns2.no-ip.com.
                                 IN MX     10    mail
                                 IN A      ~ip~
www                              IN A      ~ip~
ftp                              IN A      ~ip~
mail                             IN A      ~ip~
smtp                             IN A      ~ip~
*                                IN CNAME  www
Where the information in the SOA record will probably be provided by your dynamic DNS provider (particularly the info within the parentheses ().

The following are similar to the config entries I use for Apache:

httpd.conf:

Code: Select all

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# 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 "logs/foo.log"
# with ServerRoot set to "C:/xampp/apache" will be interpreted by the
# server as "C:/xampp/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# 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 point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/xampp/apache"

#
# 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 0.0.0.0:80
#Listen [::]:80
Listen 80

# Default charset UTF8
# AddDefaultCharset utf-8

#
# 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/mod_foo.so
#

LoadModule access_compat_module modules/mod_access_compat.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule allowmethods_module modules/mod_allowmethods.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_core_module modules/mod_authn_core.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule bucketeer_module modules/mod_bucketeer.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule case_filter_module modules/mod_case_filter.so
#LoadModule case_filter_in_module modules/mod_case_filter_in.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
LoadModule env_module modules/mod_env.so
#LoadModule example_module modules/mod_example.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule fcgid_module modules/mod_fcgid.so # did not work at runtime
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
LoadModule ssl_module modules/mod_ssl.so
LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# 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 daemon
Group daemon

</IfModule>
</IfModule>

# '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. admin@your-domain.com
#
ServerAdmin network.administrator@example.com

#
# 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 www.example.com:80

#
# 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 "C:/xampp/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>


# XAMPP: We disable operating system specific optimizations for a listening 
# socket by the http protocol here. IE 64 bit make problems without this.  
AcceptFilter http none

#
# 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.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/xampp/htdocs">
    #
    # 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
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks Includes ExecCGI

    #
    # 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 All

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.php index.pl index.cgi index.asp index.shtml index.html index.htm \
                   default.php default.pl default.cgi default.asp default.shtml default.html default.htm \
                   home.php home.pl home.cgi home.asp home.shtml home.html home.htm
</IfModule>

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

#
# 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"

#ScriptLog "logs/cgi.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
    </IfModule>

    #
    # 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>

<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 http://localhost/bar

    #
    # 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/ "C:/xampp/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock "logs/cgi.sock"
</IfModule>

#
# "C:/xampp/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/xampp/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>


<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig "conf/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 .pl .asp

    # 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
</IfModule>

<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"
</IfModule>

#
# 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/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is 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.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# XAMPP specific settings
Include "conf/extra/httpd-xampp.conf"

# Server-pool management (MPM specific)
Include "conf/extra/httpd-mpm.conf"

# Multi-language error messages
Include "conf/extra/httpd-multilang-errordoc.conf"

# Fancy directory listings
Include "conf/extra/httpd-autoindex.conf"

# Language settings
Include "conf/extra/httpd-languages.conf"

# User home directories
Include "conf/extra/httpd-userdir.conf"

# Real-time info on requests and configuration
Include "conf/extra/httpd-info.conf"

# Virtual hosts
Include "conf/extra/httpd-vhosts.conf"

# Distributed authoring and versioning (WebDAV)
# Attention! WEB_DAV is a security risk without a new userspecific configuration for a secure authentifcation 
# Include "conf/extra/httpd-dav.conf"

# Implements a proxy/gateway for Apache.
Include "conf/extra/httpd-proxy.conf"

# Various default settings
Include "conf/extra/httpd-default.conf"

# Secure (SSL/TLS) connections
Include "conf/extra/httpd-ssl.conf"
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
</IfModule>

# Configure mod_proxy_html to understand HTML4/XHTML1
#<IfModule proxy_html_module>
#Include etc/extra/proxy-html.conf
#</IfModule>

# AJP13 Proxy
<IfModule mod_proxy.c>
<IfModule mod_proxy_ajp.c>
Include "conf/extra/httpd-ajp.conf"
</IfModule>
</IfModule>
conf/extra/httpd-vhosts.conf:

Code: Select all

#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at 
# <URL:http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
#
# VirtualHost music:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost *:80>
    ProxyRequests Off
#	ProxyPreserveHost On
	ProxyPass / http://EXMPL007.ExampleLtd.local:3030/
	ProxyPassReverse / http://EXMPL007.ExampleLtd.local:3030/
#	ProxyHTMLEnable On
#	ProxyHTMLExtended On
#	ProxyHTMLURLMap http://EXMPL003.ExampleLtd.local:8080/alfresco/ /
#	ServerAdmin network.administrator@Example.com
    ##DocumentRoot "C:/xampp/htdocs/dummy-host.localhost"
    ServerName madsonic.Example.com
    ServerAlias music.Example.com
	ServerAlias media.Example.com
    ##ErrorLog "logs/docs-Example-com-error.log"
#    CustomLog "logs/docs-Example-com-access.log" combined
	##
</VirtualHost>

# VirtualHost madsonictest
<VirtualHost *:80>
    ProxyRequests Off
#	ProxyPreserveHost On
	ProxyPass / http://EXMPL009.ExampleLtd.local:4040/
	ProxyPassReverse / http://EXMPL009.ExampleLtd.local:4040/
#	ProxyHTMLEnable On
#	ProxyHTMLExtended On
#	ProxyHTMLURLMap http://EXMPL003.ExampleLtd.local:8080/alfresco/ /
#	ServerAdmin network.administrator@Example.com
    ##DocumentRoot "C:/xampp/htdocs/dummy-host.localhost"
    ServerName madsonictest.Example.com
    ServerAlias mediatest.Example.com
    ##ErrorLog "logs/docs-Example-com-error.log"
#    CustomLog "logs/docs-Example-com-access.log" combined
	##
</VirtualHost>
You should vary these to fit your particular circumstances (e.g. replace "example.com" with your external domain name and "ExampleLtd.local" with your internal domain name if you have one, otherwise use the internal ip)

You should set port forwarding on your router / modem to forward requests for port 80 (HTTP or www on some routers...) to the ip of your reverse proxy machine.

Regards
These users thanked the author bwood for the post:
Madsonic
Rating: 7.69%
gurutech
Contributor
Contributor
Posts: 323
Joined: 02 Jan 2013, 04:56
Has thanked: 11 times
Been thanked: 105 times

Re: Dual Madsonic servers?

Unread post by gurutech »

bwood wrote:There is a somewhat more flexible way to do this using a reverse proxy. It requires a "server" running Apache (XAMPP) is a good way to get a working Apache setup for Windows) - http://www.apachefriends.org/en/xampp.html.
......
You should set port forwarding on your router / modem to forward requests for port 80 (HTTP or www on some routers...) to the ip of your reverse proxy machine.

Regards
My problem is that my ISP blocks port 80, so any attempts to browse my "website" at port 80 will go unnoticed and time out. But I do want people to only need to type my website name, and not need to add the port number to the end.
bwood
Posts: 5
Joined: 10 Feb 2013, 07:09
Has thanked: 1 time
Been thanked: 3 times

Re: Dual Madsonic servers?

Unread post by bwood »

I see your problem. You could use the same approach, using :8080 as the base port, but no-ip is apparently proxying for you and since the limit for the free no-ip service is based on hosts/sub-domains, there seems to be no particular advantage to this approach for you. Others may find it useful...

Regards
Beowolf
Posts: 33
Joined: 10 Jan 2013, 15:34
Has thanked: 0
Been thanked: 2 times

Re: Dual Madsonic servers?

Unread post by Beowolf »

may i make a noob suggestion?
2 servers why?
I use mine for movies tv kids-stuff and music of course.
now Groups | Access make life easier as i have kids login who only see kids channel, friends for music and others for video of a specific nature, only allow what you want them to see.

unless you need 2 to do the same thing?
gurutech
Contributor
Contributor
Posts: 323
Joined: 02 Jan 2013, 04:56
Has thanked: 11 times
Been thanked: 105 times

Re: Dual Madsonic servers?

Unread post by gurutech »

No reason in particular, just wondering if it was possible. I know GJ51 has multiple servers running, with at least one "live" server and the others for testing.
Post Reply