You are not logged in.
Pages: 1
Hello everyone!
So I recently set up an Arch server, and while I am learning how Arch functions and where everything is located, I have a few questions about a problem I'm having. The wiki and forums are great, but I'm confused as to what the problem is that I am having. According to the way I have configured everything, I should not be having this problem. So this is my server:
If you click on that, and then click the files link, you'll get an access forbidden error. I'm thinking all the permissions are setup correctly. I can post the proper configuration files.
httpd.conf:
#
# 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.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/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/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/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"
#
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
#
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
#
# Mutex default:/run/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 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 authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authnz_fcgi_module modules/mod_authnz_fcgi.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule watchdog_module modules/mod_watchdog.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule data_module modules/mod_data.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule reflector_module modules/mod_reflector.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule deflate_module modules/mod_deflate.so
#LoadModule xml2enc_module modules/mod_xml2enc.so
#LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule mime_module modules/mod_mime.so
#LoadModule http2_module modules/mod_http2.so
#LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule logio_module modules/mod_logio.so
#LoadModule lua_module modules/mod_lua.so
LoadModule env_module modules/mod_env.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
LoadModule proxy_module modules/mod_proxy.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_fcgi_module modules/mod_proxy_fcgi.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_crypto_module modules/mod_session_crypto.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
LoadModule ssl_module modules/mod_ssl.so
#LoadModule dialup_module modules/mod_dialup.so
LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
#LoadModule mpm_event_module modules/mod_mpm_event.so
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
#LoadModule mpm_worker_module modules/mod_mpm_worker.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule heartbeat_module modules/mod_heartbeat.so
#LoadModule heartmonitor_module modules/mod_heartmonitor.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule info_module modules/mod_info.so
#LoadModule suexec_module modules/mod_suexec.so
<IfModule !mpm_prefork_module>
#LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_prefork_module>
#LoadModule cgi_module modules/mod_cgi.so
</IfModule>
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule php5_module modules/libphp5.so
#LoadModule imagemap_module modules/mod_imagemap.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
LoadModule rewrite_module modules/mod_rewrite.so
<IfModule unixd_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 http
Group http
</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@your-domain.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
#
# 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
</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.
#
#
# 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 "/srv/http"
<Directory "/srv/http">
#
# 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.4/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:
# AllowOverride FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Require all granted
</Directory>
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.html
</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 "/var/log/httpd/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 "/var/log/httpd/access_log" common
#
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog "/var/log/httpd/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://www.example.com/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/ "/srv/http/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 cgisock
</IfModule>
#
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Require all granted
</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
# 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://www.example.com/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 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: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
#EnableSendfile on
# 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
# PHP
Include conf/extra/php5_module.conf
# Owncloud
Include conf/extra/owncloud.conf
# Server
Include conf/extra/server.conf
# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf
</IfModule>
# 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>
#
# uncomment out the below to deal with user agents that deliberately
# violate open standards by misusing DNT (DNT *must* be a specific
# end-user choice)
#
#<IfModule setenvif_module>
#BrowserMatch "MSIE 10.0;" bad_DNT
#</IfModule>
#<IfModule headers_module>
#RequestHeader unset DNT env=bad_DNT
#</IfModule>
# Redirect http to https
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
server.conf: (this is the vhost for the files section, I decided to make it have its own file instead of putting it under httpd-vhosts.conf):
<IfModule mod_alias.c>
Alias /server /mnt/Storage/
</IfModule>
<Directory /mnt/Storage/>
Options FollowSymlinks
AllowOverride all
Require all granted
</Directory>
<VirtualHost *:443/server>
ServerAdmin admin@your-domain.com
DocumentRoot "/mnt/Storage"
ServerName Random@Server
ErrorLog "/var/log/httpd/server.random.info-error_log"
CustomLog "/var/log/httpd/server.random.info-access_log" common
</VirtualHost>
owncloud.conf (this is what I based my server.conf on. By specifying the Directory section, I didn't think I would have a permission issue, since /mnt/Storage (my data storage hard drive), would have its permissions set.):
<IfModule mod_alias.c>
Alias /owncloud /usr/share/webapps/owncloud/
</IfModule>
<Directory /usr/share/webapps/owncloud/>
Options FollowSymlinks
AllowOverride all
Require all granted
php_admin_value open_basedir "/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/owncloud/:/etc/webapps/owncloud:/dev/urandom:/mnt/Storage/Owncloud"
</Directory>
<VirtualHost *:443/owncloud>
ServerAdmin admin@your-domain.com
DocumentRoot /usr/share/webapps/owncloud
ServerName Random@Owncloud
ErrorLog /var/log/httpd/owncloud.random.info-error_log
CustomLog /var/log/httpd/owncloud.random.info-access_log common
</VirtualHost>
httpd-ssl.conf (since my entire apache server is using a self-signed certificate):
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailed information about these
# directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html>
#
# 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.
#
# Required modules: mod_log_config, mod_setenvif, mod_ssl,
# socache_shmcb_module (for default value of SSLSessionCache)
#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
#SSLRandomSeed startup file:/dev/random 512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random 512
#SSLRandomSeed connect file:/dev/urandom 512
#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
Listen 443
##
## SSL Global Context
##
## All SSL configuration in this context applies both to
## the main server and all SSL-enabled virtual hosts.
##
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate,
# and that httpd will negotiate as the client of a proxied server.
# See the OpenSSL documentation for a complete list of ciphers, and
# ensure these follow appropriate best practices for this deployment.
# httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers,
# while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a.
SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4
SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4
# By the end of 2016, only TLSv1.2 ciphers should remain in use.
# Older ciphers should be disallowed as soon as possible, while the
# kRSA ciphers do not offer forward secrecy. These changes inhibit
# older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy
# non-browser tooling) from successfully connecting.
#
# To restrict mod_ssl to use only TLSv1.2 ciphers, and disable
# those protocols which do not support forward secrecy, replace
# the SSLCipherSuite and SSLProxyCipherSuite directives above with
# the following two directives, as soon as practical.
# SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
# SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
# User agents such as web browsers are not configured for the user's
# own preference of either security or performance, therefore this
# must be the prerogative of the web server administrator who manages
# cpu load versus confidentiality, so enforce the server's cipher order.
SSLHonorCipherOrder on
# SSL Protocol support:
# List the protocol versions which clients are allowed to connect with.
# Disable SSLv3 by default (cf. RFC 7525 3.1.1). TLSv1 (1.0) should be
# disabled as quickly as practical. By the end of 2016, only the TLSv1.2
# protocol or later should remain in use.
SSLProtocol all -SSLv3
SSLProxyProtocol all -SSLv3
# Pass Phrase Dialog:
# Configure the pass phrase gathering process.
# The filtering dialog program (`builtin' is an internal
# terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
#SSLSessionCache "dbm:/run/httpd/ssl_scache"
SSLSessionCache "shmcb:/run/httpd/ssl_scache(512000)"
SSLSessionCacheTimeout 300
# OCSP Stapling (requires OpenSSL 0.9.8h or later)
#
# This feature is disabled by default and requires at least
# the two directives SSLUseStapling and SSLStaplingCache.
# Refer to the documentation on OCSP Stapling in the SSL/TLS
# How-To for more information.
#
# Enable stapling for all SSL-enabled servers:
#SSLUseStapling On
# Define a relatively small cache for OCSP Stapling using
# the same mechanism that is used for the SSL session cache
# above. If stapling is used with more than a few certificates,
# the size may need to be increased. (AH01929 will be logged.)
#SSLStaplingCache "shmcb:/run/httpd/ssl_stapling(32768)"
# Seconds before valid OCSP responses are expired from the cache
#SSLStaplingStandardCacheTimeout 3600
# Seconds before invalid OCSP responses are expired from the cache
#SSLStaplingErrorCacheTimeout 600
##
## SSL Virtual Host Context
##
<VirtualHost _default_:443>
# General setup for the virtual host
DocumentRoot "/srv/http"
ServerName Random
ServerAdmin admin@your-domain.com
ErrorLog "/var/log/httpd/ssl.random.info-error_log"
TransferLog "/var/log/httpd/ssl.random.info-access_log"
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate. If
# the certificate is encrypted, then you will be prompted for a
# pass phrase. Note that a kill -HUP will prompt again. Keep
# in mind that if you have both an RSA and a DSA certificate you
# can configure both in parallel (to also allow the use of DSA
# ciphers, etc.)
# Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
# require an ECC certificate which can also be configured in
# parallel.
SSLCertificateFile "/etc/ssl/certs/MediaServer363.ddns.net.pem"
#SSLCertificateFile "/etc/httpd/conf/server-dsa.crt"
#SSLCertificateFile "/etc/httpd/conf/server-ecc.crt"
# Server Private Key:
# If the key is not combined with the certificate, use this
# directive to point at the key file. Keep in mind that if
# you've both a RSA and a DSA private key you can configure
# both in parallel (to also allow the use of DSA ciphers, etc.)
# ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile "/etc/ssl/private/key.pem"
#SSLCertificateKeyFile "/etc/httpd/conf/server-dsa.key"
#SSLCertificateKeyFile "/etc/httpd/conf/server-ecc.key"
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convenience.
#SSLCertificateChainFile "/etc/httpd/conf/server-ca.crt"
# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
# Note: Inside SSLCACertificatePath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCACertificatePath "/etc/httpd/conf/ssl.crt"
#SSLCACertificateFile "/etc/httpd/conf/ssl.crt/ca-bundle.crt"
# Certificate Revocation Lists (CRL):
# Set the CA revocation path where to find CA CRLs for client
# authentication or alternatively one huge file containing all
# of them (file must be PEM encoded).
# The CRL checking mode needs to be configured explicitly
# through SSLCARevocationCheck (defaults to "none" otherwise).
# Note: Inside SSLCARevocationPath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCARevocationPath "/etc/httpd/conf/ssl.crl"
#SSLCARevocationFile "/etc/httpd/conf/ssl.crl/ca-bundle.crl"
#SSLCARevocationCheck chain
# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10
# TLS-SRP mutual authentication:
# Enable TLS-SRP and set the path to the OpenSSL SRP verifier
# file (containing login information for SRP user accounts).
# Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for
# detailed instructions on creating this file. Example:
# "openssl srp -srpvfile /etc/httpd/conf/passwd.srpv -add username"
#SSLSRPVerifierFile "/etc/httpd/conf/passwd.srpv"
# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>
# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory "/srv/http/cgi-bin">
SSLOptions +StdEnvVars
</Directory>
# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is sent or allowed to be received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
BrowserMatch "MSIE [2-5]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# Per-Server Logging:
# The home of a custom SSL log file. Use this when you want a
# compact non-error SSL logfile on a virtual host basis.
CustomLog "/var/log/httpd/ssl_request_log" \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
</VirtualHost>
permissions of /mnt/Storage:
drwxrwxr-x 9 username users 4096 Oct 31 03:53 Storage
Let me know if more information will be helpful. But judging from all this, I shouldn't have any issues. Unless I'm missing something, which I must be. I just don't know what it is.
Last edited by TheDrifter363 (2019-08-12 08:49:56)
Offline
Hello drifter,
welcome to archlinux, which is a good choice!
About your issue, I don't think that the server configuration is the issue.
You just don't have an index document in /mnt/storage as the errormessage already mentions!
> You don't have permission to access the requested directory. ____There is either no index document or the directory is read-protected. ____
So you could either add an index.html / index.php to provide some content or allow apache to list the directory content.
Here is the setting you need: https://httpd.apache.org/docs/2.4/mod/core.html#options
Last edited by debijan (2015-11-01 12:56:19)
Offline
You are running https only? http should work, but you seem to have it disabled. The error from firefox
random363.ddns.net uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for MediaServer363.ddns.net
This sounds just like my issue from not understanding how https worked. You will need to match your CN name to the url, and register with a certificate authority for https.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I too had the bad certificate, but I created an exception and overrode it. Then I reached your site.
Yes, there are a couple directories that are forbidden. By default, everything starts that way.
To make the server directory available, you will need to add this to /etc/httpd/conf/httpd.conf
<Directory /srv/http/server>
Require all granted
</Directory>
and restart the server. Note that this assumes you are still using the default document root (/srv/http/) and that the /srv/http/server exists.
Repeat for the other directories.
Now, as to those services that use different ports.... You can link to them, but they are not served by Apache. I tried one and it would appear that you have them blocked at your firewall.
Edit: Oh, I missed your alias. Not sure exactly how that works.
Last edited by ewaller (2015-11-01 15:09:34)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Hey, I noticed that you fixed whatever issue you were having. One thing I would suggest would be to password protect your transmission client. Possibly also hide it behind an apache vhost acting as a reverse proxy so you can access through port 80 or 443.
Offline
Hello drifter,
welcome to archlinux, which is a good choice!
About your issue, I don't think that the server configuration is the issue.
You just don't have an index document in /mnt/storage as the errormessage already mentions!
> You don't have permission to access the requested directory. ____There is either no index document or the directory is read-protected. ____So you could either add an index.html / index.php to provide some content or allow apache to list the directory content.
Here is the setting you need: https://httpd.apache.org/docs/2.4/mod/core.html#options
Thank you so very much! Apparently I had to add a simple option:
Options FollowSymlinks Indexes
The Indexes part allowed apache to list files. I can't believe I missed such a simple step. *facepalm*
You are running https only? http should work, but you seem to have it disabled. The error from firefox
random363.ddns.net uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for MediaServer363.ddns.net
This sounds just like my issue from not understanding how https worked. You will need to match your CN name to the url, and register with a certificate authority for https.
I remember reading your dilemma when I was hunting for a way to fix my error. I remember thinking that you should be able to add an exception to any self signed certificate so you don't have to pay money to the CN authority. I think someone also linked something about a new authority sponsored by the EFF, which I think is great. I use firefox, so an exception is easy, but I don't know how the other browsers handle self signed certificates. I prefer https, as I heard it is more secure.
I too had the bad certificate, but I created an exception and overrode it. Then I reached your site.
Yes, there are a couple directories that are forbidden. By default, everything starts that way.
To make the server directory available, you will need to add this to /etc/httpd/conf/httpd.conf<Directory /srv/http/server> Require all granted </Directory>
and restart the server. Note that this assumes you are still using the default document root (/srv/http/) and that the /srv/http/server exists.
Repeat for the other directories.Now, as to those services that use different ports.... You can link to them, but they are not served by Apache. I tried one and it would appear that you have them blocked at your firewall.
Edit: Oh, I missed your alias. Not sure exactly how that works.
Yeah, I don't know really know how that alias thing works either. I added it just because the owncloud.conf had it. If I get rid of it, the server still works fine, everything redirects where it needs to be. I am still using the /srv/http as my main apache directory. I initially had my /mnt/Storage symlinked there, but I thought it was a bit unorganized. I like everything neat. Lol. So then I thought about the approach I'm currently taking, with the server directory having its own config file and its own access.
Hey, I noticed that you fixed whatever issue you were having. One thing I would suggest would be to password protect your transmission client. Possibly also hide it behind an apache vhost acting as a reverse proxy so you can access through port 80 or 443.
Yeah I totally did thanks to the help of the first reply! In fact I just woke up and tried it out right now. I would like if transmission was behind the same https, but I have no idea how to do that. The transmission web interface doesn't natively support https. I would have to figure out how to do what you are suggesting. Though my transmission client is password protected. Are you able to see my torrents? It should request for a password. Hmm....that's a problem.
Also it would be great if all of my services could be serviced under apache vhosts file. I'll have to see if such a thing can be done. It would ease my need for port forwarding. These include owncloud, emby, and webmin. Time to research!
By the way, thank you all for your help and suggestions, I will take it to heart.
Last edited by TheDrifter363 (2015-11-01 17:06:49)
Offline
I too see that you have fixed the problem. Great.
But... Looking at your extensive collection, I seriously recommend you take that site down. If those files are what they seem to be (I did not download any), you do not have the rights to offer them for upload and will get you in serious trouble with the copyright holders. I am so concerned about this, I am seriously wondering if I should redact the link to your site from this thread. I am not suggesting (yet) that you could be afoul our rules, but consider carefully what you are doing. Comments?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I too see that you have fixed the problem. Great.
But... Looking at your extensive collection, I seriously recommend you take that site down. If those files are what they seem to be (I did not download any), you do not have the rights to offer them for upload and will get you in serious trouble with the copyright holders. I am so concerned about this, I am seriously wondering if I should redact the link to your site from this thread. I am not suggesting (yet) that you could be afoul our rules, but consider carefully what you are doing. Comments?
Oh, my sincere apologies. I have taken it down as requested.
Offline
No apologies required. I just felt the obligation to point out that hosting those files, even as a learning experience, could get you quickly up to your eyeballs in Bandini
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
No apologies required. I just felt the obligation to point out that hosting those files, even as a learning experience, could get you quickly up to your eyeballs in Bandini
Oh, that is very unfortunate. So sorry. Thank you for your concern, though, it is appreciated.
I was going to ask for your help with my transmission client, but apparently I figured out the issue. I had rpc authenticated required set to false. Ugh....such a simple mistake.
Ok so now, my transmission client should be secured. Now I just have to figure out how to set it up as vhost or set it up using https.
Thanks again everyone!
PS: The server is back up, but hopefully I removed any offending content. Feel free to critique.
Last edited by TheDrifter363 (2015-11-01 17:35:03)
Offline
ewaller wrote:No apologies required. I just felt the obligation to point out that hosting those files, even as a learning experience, could get you quickly up to your eyeballs in Bandini
Oh, that is very unfortunate. So sorry. Thank you for your concern, though, it is appreciated.
I was going to ask for your help with my transmission client, but apparently I figured out the issue. I had rpc authenticated required set to false. Ugh....such a simple mistake.
Ok so now, my transmission client should be secured. Now I just have to figure out how to set it up as vhost or set it up using https.
Thanks again everyone!
PS: The server is back up, but hopefully I removed any offending content. Feel free to critique.
Your transmission client does appear to be password protected, but since it's served over 80, it would be trivial for someone to view your username and password using a tool like Wireshark. Re: setting up apache proxies, it's usually simple to do depending on the way the application is served. Some require more complex setups than others. I actually proxy transmission with apache over https. It's pretty simple and I can provide you the config file if you would like but I recommend you learn to do this on your own. There should be enough documentation and examples out there to figure it out. I'm certainly happy to answer any questions you have about it. But once you figure out how to proxy one host, it's usually pretty easy to go from there and apply the same technique to the rest of your hosts.
Offline
Your transmission client does appear to be password protected, but since it's served over 80, it would be trivial for someone to view your username and password using a tool like Wireshark. Re: setting up apache proxies, it's usually simple to do depending on the way the application is served. Some require more complex setups than others. I actually proxy transmission with apache over https. It's pretty simple and I can provide you the config file if you would like but I recommend you learn to do this on your own. There should be enough documentation and examples out there to figure it out. I'm certainly happy to answer any questions you have about it. But once you figure out how to proxy one host, it's usually pretty easy to go from there and apply the same technique to the rest of your hosts.
Ok, so this is my current transmission.conf. I've included an Include statement in httpd.conf, so that's not a problem. I'm having trouble getting this to work though. I think it's because I'm not understanding how this whole thing works and how to manipulate it to my needs.
<VirtualHost *:443/transmission>
ServerAdmin admin@your-domain.com
ServerName Random@Transmission
ErrorLog "/var/log/httpd/transmission.random.info-error_log"
CustomLog "/var/log/httpd/transmission.random.info-access_log" common
ProxyPass /transmission http://random363.ddns.net:9091/transmission
ProxyPassReverse /transmission http://random363.ddns.net:9091/transmission
</VirtualHost>
I don't know if a wild card can be placed for the url under ProxyPass like http://*:9091. I'd be interested in anyone's help.
Last edited by TheDrifter363 (2019-08-12 08:51:40)
Offline
cris9288 wrote:Your transmission client does appear to be password protected, but since it's served over 80, it would be trivial for someone to view your username and password using a tool like Wireshark. Re: setting up apache proxies, it's usually simple to do depending on the way the application is served. Some require more complex setups than others. I actually proxy transmission with apache over https. It's pretty simple and I can provide you the config file if you would like but I recommend you learn to do this on your own. There should be enough documentation and examples out there to figure it out. I'm certainly happy to answer any questions you have about it. But once you figure out how to proxy one host, it's usually pretty easy to go from there and apply the same technique to the rest of your hosts.
Ok, so this is my current transmission.conf. I've included an Include statement in httpd.conf, so that's not a problem. I'm having trouble getting this to work though. I think it's because I'm not understanding how this whole thing works and how to manipulate it to my needs.
<VirtualHost *:443/transmission> ServerAdmin lilenz2637@aol.com ServerName Random@Transmission ErrorLog "/var/log/httpd/transmission.random.info-error_log" CustomLog "/var/log/httpd/transmission.random.info-access_log" common ProxyPass /transmission http://random363.ddns.net:9091/transmission ProxyPassReverse /transmission http://random363.ddns.net:9091/transmission </VirtualHost>
I don't know if a wild card can be placed for the url under ProxyPass like http://*:9091. I'd be interested in anyone's help.
That should almost work. I know that when I set this up, I used my machine's local IP address and transmission port - so for example http://192.168.0.3:9091 rather than the host name. I think there is a problem with your router sending out packets addressed to itself.
Last edited by cris9288 (2015-11-01 23:24:02)
Offline
That should almost work. I know that when I set this up, I used my machine's local IP address and transmission port - so for example http://192.168.0.3:9091 rather than the host name. I think there is a problem with your router sending out packets addressed to itself.
Ok so I am at a loss. Lol. I've spent all day trying to figure this out, and I don't know why it doesn't work. I wonder if it has to do with my VirtualHost *:443/transmission, but I'm not certain.
transmission.conf:
<VirtualHost *:443/transmission>
ServerAdmin admin@your-domain.com
ServerName Random@Transmission
ErrorLog "/var/log/httpd/transmission.random.info-error_log"
CustomLog "/var/log/httpd/transmission.random.info-access_log" common
ProxyPass /transmission http://192.168.1.250:9091
ProxyPassReverse /transmission http://192.168.1.250:9091
</VirtualHost>
I have no idea how to make this work. Any help would be much appreciated.
Last edited by TheDrifter363 (2019-08-12 08:52:04)
Offline
cris9288 wrote:That should almost work. I know that when I set this up, I used my machine's local IP address and transmission port - so for example http://192.168.0.3:9091 rather than the host name. I think there is a problem with your router sending out packets addressed to itself.
Ok so I am at a loss. Lol. I've spent all day trying to figure this out, and I don't know why it doesn't work. I wonder if it has to do with my VirtualHost *:443/transmission, but I'm not certain.
transmission.conf:
<VirtualHost *:443/transmission> ServerAdmin lilenz2637@aol.com ServerName Random@Transmission ErrorLog "/var/log/httpd/transmission.random.info-error_log" CustomLog "/var/log/httpd/transmission.random.info-access_log" common ProxyPass /transmission http://192.168.1.250:9091 ProxyPassReverse /transmission http://192.168.1.250:9091 </VirtualHost>
I have no idea how to make this work. Any help would be much appreciated.
Well, here's mine. I think it's just the "/transmission" bit in the VirtualHost tag and the ProxyPass* directives that could be throwing you off. I would check the logs that you point to in the vhost config.
SSLStrictSNIVHostCheck off
<VirtualHost *:443>
ServerName my.torrent.host:443
SSLEngine on
SSLCertificateFile "/etc/httpd/conf/server.crt"
SSLCertificateKeyFile "/etc/httpd/conf/server.key"
ProxyPass / http://192.168.0.17:9091/
</VirtualHost>
FYI, the SSLStrictSNIVHostCheck option is documented here. https://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI. I'm not 100% it's necessary in your case (or mine), but it's just been there for a long time. Anyways, hope that helps.
Last edited by cris9288 (2015-11-02 04:41:10)
Offline
Well, here's mine. I think it's just the "/transmission" bit in the VirtualHost tag and the ProxyPass* directives that could be throwing you off. I would check the logs that you point to in the vhost config.
SSLStrictSNIVHostCheck off <VirtualHost *:443> ServerName my.torrent.host:443 SSLEngine on SSLCertificateFile "/etc/httpd/conf/server.crt" SSLCertificateKeyFile "/etc/httpd/conf/server.key" ProxyPass / http://192.168.0.17:9091/ </VirtualHost>
FYI, the SSLStrictSNIVHostCheck option is documented here. https://wiki.apache.org/httpd/NameBasedSSLVHostsWithSNI. I'm not 100% it's necessary in your case (or mine), but it's just been there for a long time. Anyways, hope that helps.
So I finally got it to work! Yay! It took all day yesterday, was finished right before I went to bed. I'll show you my transmission.conf. Hopefully it will help others. Also I modified my owncloud and server conf files in order to make everything neater. Unfortunately I couldn't add the port number in the servername, otherwise that virtual host would take priority and show up when I typed in random363.ddns.net. I have no idea why, but its working for right now. Check it out.
transmission.conf:
<VirtualHost *:443>
ServerAdmin admin@your-domain.com
ServerName random363.ddns.net:443/transmission
ErrorLog "/var/log/httpd/transmission.random.info-error_log"
CustomLog "/var/log/httpd/transmission.random.info-access_log" common
SSLEngine on
SSLCertificateFile "/etc/ssl/certs/MediaServer363.ddns.net.pem"
SSLCertificateKeyFile "/etc/ssl/private/key.pem"
ProxyPass /transmission http://localhost:9091/transmission
</VirtualHost>
server.conf
<IfModule mod_alias.c>
Alias /server /mnt/Storage
</IfModule>
<Directory /mnt/Storage>
Options FollowSymlinks Indexes
AllowOverride all
Require all granted
</Directory>
<VirtualHost *:443>
ServerAdmin admin@your-domain.com
DocumentRoot "/mnt/Storage"
ServerName random363.ddns.net/server
ErrorLog "/var/log/httpd/server.random.info-error_log"
CustomLog "/var/log/httpd/server.random.info-access_log" common
SSLEngine on
SSLCertificateFile "/etc/ssl/certs/MediaServer363.ddns.net.pem"
SSLCertificateKeyFile "/etc/ssl/private/key.pem"
</VirtualHost>
owncloud.conf
<IfModule mod_alias.c>
Alias /owncloud /usr/share/webapps/owncloud
</IfModule>
<Directory /usr/share/webapps/owncloud>
Options FollowSymlinks
AllowOverride all
Require all granted
php_admin_value open_basedir "/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/owncloud/:/etc/webapps/owncloud:/dev/urandom:/mnt/Storage/Owncloud"
</Directory>
<VirtualHost *:443>
ServerAdmin admin@your-domain.com
DocumentRoot /usr/share/webapps/owncloud
ServerName random363.ddns.net/owncloud
ErrorLog /var/log/httpd/owncloud.random.info-error_log
CustomLog /var/log/httpd/owncloud.random.info-access_log common
SSLEngine on
SSLCertificateFile "/etc/ssl/certs/MediaServer363.ddns.net.pem"
SSLCertificateKeyFile "/etc/ssl/private/key.pem"
</VirtualHost>
Hopefully this will be better. I plan to also add emby and webmin under this apache proxy system. It would be a lot neater.
Last edited by TheDrifter363 (2019-08-12 08:53:15)
Offline
Pages: 1