[SOLVED] lamp - symlink not working?

exequtor · 2016-03-14 07:03:09

When I installed BL, I was prompted to install lamp in the welcome script and accepted it.

Now, when I go to http://localhost/ - I can see the Apache2 Debian Default Page
I can even see PHPmyAdmin when I go to http://localhost/phpmyadmin/

The symlink is pointing to /home/myusername/htdocs

But when I try to access and go to http://localhost/myusername/ - I get a 404 error.

What do you guys thinks?

Last edited by exequtor (2016-03-15 12:30:27)

nobody · 2016-03-14 12:45:24

exequtor wrote:

What do you guys thinks?

Not much, unless you pass us the full apache2 configuration which invokes that behaviour. Whatever gets set up by the lamp option, it just installs the Debian packages and leaves everything as the packages set it up.

exequtor · 2016-03-14 13:00:37

Where do I find the apache2 configuration?

Sorry for the n00b question but I just started learning and getting familiar with Linux.

Thank you.

xaos52 · 2016-03-14 13:28:34

^ The main apache2 config file is at

/etc/apache2/apache2.conf

johnraff · 2016-03-15 02:33:23

First of all, have you got any files in /home/myusername/htdocs? Try copying in /var/www/index.html, see if that now works, and go from there.

exequtor · 2016-03-15 05:16:40

Here it is:

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# 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 ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

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


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

exequtor · 2016-03-15 05:18:06

johnraff wrote:

First of all, have you got any files in /home/myusername/htdocs? Try copying in /var/www/index.html, see if that now works, and go from there.

Yes, I have index.php with phpinfo() in it.

johnraff · 2016-03-15 07:59:31

^I just tried making /var/www/john and copying index.html from /var/www to there and http://localhost/john came up OK. Maybe you have to enable php for index.php to work.

xaos52 · 2016-03-15 08:09:23

But when I try to access and go to http://localhost/myusername/ - I get a 404 error.

This is perfectly normal!
In that setup a request for http://localhost is 'routed' by the apache server to /home/myusername/htdocs.

When you request http://localhost/myusername, the server routes you to /home/myusername/htdocs/myusername, and that directory does not exist.

john wrote:

^I just tried making /var/www/john and copying index.html from /var/www to there and http://localhost/john came up OK. Maybe you have to enable php for index.php to work.

This works because http://localhost/john gets routed to /home/yourusername/htdocs/john, and /home/username/htdocs is a symlink to /var/www, so the dir exists.

exequtor · 2016-03-15 08:35:43

xaos52 wrote:

This is perfectly normal!
In that setup a request for http://localhost is 'routed' by the apache server to /home/myusername/htdocs.
When you request http://localhost/myusername, the server routes you to /home/myusername/htdocs/myusername, and that directory does not exist.

This doesn't work though.

I was expecting the automated process to setup lamp with symlinks in BL to work out-of-the-box, but I was wrong. Anyway, I'm working in /var/www/html now and followed everything from here.

But I would love to have the ability to have my work inside my home directory instead anywhere within /var/www/* as I wouldn't want to tamper with the permissions, which I ended up doing.

johnraff · 2016-03-15 08:44:54

^^well actually I never made such a symlink in my setup, and I have no /home/john/htdocs directory. I just made a subdir of /var/www to test if the lack of an html file might be the issue. My own local sites' (as virtualhosts) files are somewhere else entirely, with the paths set in files in /etc/apache2/sites-available.

@exequtor what you were trying to do sounds perfectly reasonable, and I see no reason why you can't put files in ~/htdocs if you have the symlink from /var/www/<username>

exequtor · 2016-03-15 08:50:22

johnraff wrote:

@exequtor what you were trying to do sounds perfectly reasonable, and I see no reason why you can't put files in ~/htdocs if you have the symlink from /var/www/<username>

I'm able to put files in /home/exequtor/htdocs without a problem. The problem is I'm not able to see them in localhost.

xaos52 · 2016-03-15 08:51:59

exequtor wrote:

The symlink is pointing to /home/myusername/htdocs

OP has that symlink
When he puts his html files immediately under /home/myusername/htdocs, and request them with
http://localhost that should work. And it is what he wants, if I understand correctly.

OP:
Request them with
http::/localhost

NOT
http://localhost/myusername

UNLESS

of course if you created /home/myusername/htdoc/myusername
and created your html below that directory.

exequtor · 2016-03-15 09:14:56

xaos52 wrote:

OP has that symlink
When he puts his html files immediately under /home/myusername/htdocs, and request them with
http://localhost that should work. And it is what he wants, if I understand correctly.

Yes, that is correct. Only it doesn't work.

http://localhost/

- loads the default debian apache page (/var/www/html/index.html)

http://localhost/phpmyadmin/

- even this one works

http://localhost/exequtor/

- 404 error

- I've placed files and folders in there (/var/www/exequtor --> /home/exequtor/htdocs) but none seems to be working.

xaos52 · 2016-03-15 11:31:31

Ah, I see.
You need to change your DocumentRoot.

I don't know what the recommended method is - I don't use apache2 - you can either create a new virtualhost or change the Documentroot for the default virtualhost.

For the latter:
Edit as root: /etc/apache2/sites-available/000default.conf to

<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com

	ServerAdmin webmaster@localhost
	# DocumentRoot /var/www/html
        DocumentRoot /var/www

	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

I have commented out the original DocumentRoot and added the new one.

Restart apache2 and things should work.

WARNING:
I suspect this is not the safest way to configure apache2.
The recommended way may be to create a new virtualhost in /etc/apache2/sites-available, then run a2ensite to enable it, and restart apache2 to activate it.

exequtor · 2016-03-15 12:30:02

That solved it!

So basically, just changing the DocumentRoot value.

# DocumentRoot /var/www/html
DocumentRoot /var/www

Thank you!!!

xaos52 wrote:

Ah, I see.
You need to change your DocumentRoot.
I don't know what the recommended method is - I don't use apache2 - you can either create a new virtualhost or change the Documentroot for the default virtualhost.
For the latter:
Edit as root: /etc/apache2/sites-available/000default.conf to
<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com

	ServerAdmin webmaster@localhost
	# DocumentRoot /var/www/html
        DocumentRoot /var/www

	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
I have commented out the original DocumentRoot and added the new one.
Restart apache2 and things should work.
WARNING:
I suspect this is not the safest way to configure apache2.
The recommended way may be to create a new virtualhost in /etc/apache2/sites-available, then run a2ensite to enable it, and restart apache2 to activate it.

johnraff · 2016-03-15 23:40:01

If you use the DocumentRoot setting you don't need that symlink at all. You can put the files anywhere you want.

#1 2016-03-14 07:03:09

[SOLVED] lamp - symlink not working?

#2 2016-03-14 12:45:24

Re: [SOLVED] lamp - symlink not working?

#3 2016-03-14 13:00:37

Re: [SOLVED] lamp - symlink not working?

#4 2016-03-14 13:28:34

Re: [SOLVED] lamp - symlink not working?

#5 2016-03-15 02:33:23

Re: [SOLVED] lamp - symlink not working?

#6 2016-03-15 05:16:40

Re: [SOLVED] lamp - symlink not working?

#7 2016-03-15 05:18:06

Re: [SOLVED] lamp - symlink not working?

#8 2016-03-15 07:59:31

Re: [SOLVED] lamp - symlink not working?

#9 2016-03-15 08:09:23

Re: [SOLVED] lamp - symlink not working?

#10 2016-03-15 08:35:43

Re: [SOLVED] lamp - symlink not working?

#11 2016-03-15 08:44:54

Re: [SOLVED] lamp - symlink not working?

#12 2016-03-15 08:50:22

Re: [SOLVED] lamp - symlink not working?

#13 2016-03-15 08:51:59

Re: [SOLVED] lamp - symlink not working?

#14 2016-03-15 09:14:56

Re: [SOLVED] lamp - symlink not working?

#15 2016-03-15 11:31:31

Re: [SOLVED] lamp - symlink not working?

#16 2016-03-15 12:30:02

Re: [SOLVED] lamp - symlink not working?

#17 2016-03-15 23:40:01

Re: [SOLVED] lamp - symlink not working?

Board footer