Board index » America's Army: Legacy Versions » AA3 - Server Support




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 20 posts ]  Go to page Previous  1, 2
Author Message
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 7:11 pm 
Offline

Joined: Tue Feb 26, 2008 2:28 am
Posts: 63
Location: Michigan
That isn't a normal default Apache setup ... did you, by chance, use another member's suggestion of XAMPP, instead of just installing Apache like I mentioned? I cannot support that setup since I have no clue what it did during installation. You only needed Apache.

I am not sure how that's going to work, or even if it will work at all.

*EDITED* Removed redundant information and an invalid config comment. *EDITED*

I also noticed that you assigned port 81 ... you will need to specify that in your URL call: http://81.99.249.239:81/svss/

Last thing, since your web server does not function, you'll need to visit ?XAMPP? support to get that working first. http://81.99.249.239:81/ should have produced a page or some kind of response.

Easy inspection;
Is port 81 open through your firewall and all other security utilities?
Is the Apache service currently running?
Does the default index page @ http://81.99.249.239:81/ display "It Works!"?

This is assuming that your WAN / public IP is 81.99.249.239, of course.


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 7:50 pm 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
Can you suggest which apache i use, maybe supply the link to the version that you use?


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 8:48 pm 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
Ok ive put a copy of Apache 2.2 (after removing XAMPP from system). Service seems to be running as when i goto "http://localhost" or just type in "192.168.0.4) into browser on the server machine, I get the "It Works!" message up on my browser. However Im still unsure why Im not being able to get the svss folder to appear as a web page when I attempt to browse to it in my browser. So heres the httpd.conf file for inspection, Im pretty sure I am almost there but just need that little nudge to get it spot on.

#
# 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:/Apache" will be interpreted by the
# server as "C:/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:/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 12.34.56.78:80
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/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.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_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.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 cache_module modules/mod_cache.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 env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#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 proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.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 admin@rebel-gamers.net

#
# 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 81.99.249.239: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:/Apache/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>

#
# 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:/Apache/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

#
# 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.
#
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 pbsvss.htm
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>

#
# 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
</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://81.99.249.239/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
Alias /svss "C:/Servers/aa3/Binaries/pb/svss/"
#
# 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:/Apache/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/cgisock
</IfModule>

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

# "C:/Servers/aa3/Binaries/pb/svss" should be changed to whatever your Alias is
<Directory "/svss">
AllowOverride All
Options All Multiviews
Order allow,deny
Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<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

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

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

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

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

# 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

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.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>


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 8:54 pm 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
Ive now forwarded port 81 to the lan ip in my router and if i browse to my wan ip of 81.99.249.239 i get the "It works!" message, however if i attempt to go to the svss folder I get a forbidden message.


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 10:24 pm 
Offline

Joined: Tue Feb 26, 2008 2:28 am
Posts: 63
Location: Michigan
seems your port in the configuration just above this, is listed as 80, maybe change that to 81

I noticed an error in my example and I will adjust that in a moment. The error is simple :) just change the following;
Code:
# "/svss" should be changed to the full folder path
<Directory "C:/Servers/aa3/Binaries/pb/svss">
AllowOverride All
Options All Multiviews
Order allow,deny
Allow from all
</Directory>
.


Then restart your Apache server and it should be a go! (the configuration only needs two adjustments, port and path).


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Fri Feb 01, 2013 10:58 pm 
Offline

Joined: Thu Apr 14, 2011 6:31 pm
Posts: 982
This script works for those that want to upload there servers pb screenshots to a remote website for example there clan website, ISP provided webspace or DropBox.
It does not require Apache or any special server privileges thus perfect for those who rent game servers from a game server provider.

Step 1:
Find the "pbsvgame.cfg" file on your AA3 server (may change depending on what 3rd party anti cheat scripts you run)

Step 2:
Add the following text to the .cfg file:
Quote:
pb_sv_sscmd pb\get_pbss.bat


Step 3:
Save and upload over original file.

Step 4:
Open notepad and copy/paste the following:
Quote:
rem America's Army 3 Screenshots Uploader by RollingInTheHurt.
rem "homedir=" is the defult hd where the servers AA3 is installed.
rem "aa3dir=" is the path to where the AA3 server is installed.
rem "ftpuser=" is the remote username to login to an FTP server be it locally or remote ie. your clan webhosting.
rem "ftppass=" is the remote password to login to an FTP server be it locally or remote ie. your clan webhosting.
rem "ftpserver=" is the remote address to login to an FTP server be it locally or remote ie. your clan webhosting.
rem //SETTINGS VARIBLES//
set homedir=c:\
set aa3dir=c:\whine\aah3\Binaries\
set ftpuser=myclanusernamehere@myclanwebsite.com
set ftppass=myclanpasswordhere
set ftpserver=ftp.myclanwebsite.com

rem //ABORTING IF NO SCREENSHOT EXISTS//
if not exist %aa3dir%\pb\svss\*.png goto clean-up
rem //RENAMING PB SCREENSHOTS//
cd %aa3dir%\pb\svss
for %%i in (*.png) do ren %%i %random%_%%i
cd %homedir%

rem //BUILD FTP COMMANDS TO LOG//
echo open %ftpserver%> aa3_pbscreenshot_uploader.txt
echo %ftpuser%>> aa3_pbscreenshot_uploader.txt
echo %ftppass%>> aa3_pbscreenshot_uploader.txt
echo prompt>> aa3_pbscreenshot_uploader.txt
echo type binary>> aa3_pbscreenshot_uploader.txt
echo cd /logs>> aa3_pbscreenshot_uploader.txt
rem //SELECTING PB SCREENSHOTS//
echo mput %aa3dir%\pb\svss\*.png>> aa3_pbscreenshot_uploader.txt
echo bye>> aa3_pbscreenshot_uploader.txt

rem //UPLOAD ALL SCREENSHOTS TO REMOTE HOST//
ftp -s:aa3_pbscreenshot_uploader.txt

rem //DELET LOCAL PB SCREENSHOTS AFTER UPLOAD//
del %aa3dir%\pb\svss\*.png /q
del %aa3dir%\pb\svss\*.htm /q

rem //CLEANING UP//
:clean-up
set homedir=
set aa3dir=
set ftpserver=
set ftpuser=
set ftppass=
del aa3_pbscreenshot_uploader.txt


Step 5:
Save file as "get_ss.bat" and upload to your servers PB directory.

Step 6:
Cold Restart game server and wait for screenshots to be uploaded remotely.


**Edit, changed from [code] bbcode to [quote] for easier viewing.

_________________
Image


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Sat Feb 02, 2013 12:07 am 
Offline

Joined: Tue Feb 26, 2008 2:28 am
Posts: 63
Location: Michigan
There are only three edits to be made;

  1. Change Listen 80 to Listen 81
  2. Change ServerName 81.99.249.239:80 to ServerName 81.99.249.239:81
  3. Change <Directory "/svss"> to <Directory "C:/Servers/aa3/Binaries/pb/svss">
  4. Restart the server using the Apache service monitor.
  5. Click this to verify success: http://81.99.249.239:81/svss/


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Sat Feb 02, 2013 1:34 am 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
Yer sorry the config I loaded up here shows as 80, I then readjusted that to port 81 but didnt change it here. So need to follow steps 3 thru 5 and see how it goes :)


Last edited by leegreaves on Sat Feb 02, 2013 12:31 pm, edited 1 time in total.

Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Sat Feb 02, 2013 1:36 am 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
Hooah! it works!

Cheers Sammy! Again a great help youve been!!

Many thanks!


Top 
 Profile  
 
 Post subject: Re: How to make screenshots viewable
 Post Posted: Sun Feb 03, 2013 1:16 pm 
Offline

Joined: Sat May 10, 2008 9:01 pm
Posts: 106
I finally worked out WHY my webserver wouldnt work when using Xampp.

Apache 2.2.x which I reverted to uses the OLD method of accepting/denying webpath permissions

Quote:
# "C:/Servers/aa3/Binaries/pb/svss" should be changed to whatever your Alias is
<Directory "/svss">
AllowOverride All
Options All Multiviews
Order allow,deny
Allow from all

</Directory>


Whereas the newer versions word this differently using the Require command!

Quote:
# "C:/Servers/aa3/Binaries/pb/svss" should be changed to whatever your Alias is
<Directory "/svss">
AllowOverride All
Options All Multiviews
Require all granted
</Directory>


I changed just these TWO lines of code and now I have it up and running as it should be!

The reason Ive chosen Xampp over a native Apache installation is the "user friendly" GUI and the fact that it comes with integrated MySQL/PHP MyAdmin/Tomcat/Perl and Mercury mail server.


Top 
 Profile  
 
Display posts from previous:  Sort by  
 
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 20 posts ]  Go to page Previous  1, 2

Board index » America's Army: Legacy Versions » AA3 - Server Support


Who is online

Users browsing this forum: No registered users and 1 guest

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
cron