Tag Info

New answers tagged

1

Me too. Slim pickings on this. I do think that Redhat/Fedora/CentOS has more of that stuff included - it's got a "HTTP - Virtual Host" configurator gui tool that's rather Windows-like. What I've found so far: Full featured Java apps are "Netloony" and "Apache GUI" http://netloony.sourceforge.net/ http://apachegui.net/Home.html Minimal panel apps in ...


0

Go to this file /etc/apache2/apache2.conf and add follwing lines End of the file ServerName localhost This will set the server directive Globally.


1

Probably at line 20 of /etc/apache2/sites-enabled/zzz-deny-generic.conf is present something like: ServerName * According to Apache documentation, ServerName syntax is: ServerName [scheme://]fully-qualified-domain-name[:port] As I can understand this last configuration file would deny any request that is not matched by previous VirtualHost. ...


0

According to Apache documentation: If no ServerName is specified, then the server attempts to deduce the hostname by performing a reverse lookup on the IP address. Reverse lookup: Look up an IP address to find the domain name for the IP address. I guess that this is why example.de is served by your default VirtualHost, so try to add ServerName ...


1

You need to enable the directory explicitly in your /etc/apache2/apache2.conf Find the section that reads like this: <Directory /usr/share/or_whatever > Allow override none Require all granted </Directory> where granted or denied is the explicit permission for this non-standard directory. Without this directive everything outside of ...


0

It is not a security risk, you may secure /home/me/sites the same way as you do /var/www. Sometimes on servers /home may be on different partition with different size than /var and disk usage or performance optimization may come to consideration.


1

The location where config files for Apache are stored in Ubuntu by default, is already only writeable by the root user. The files however, must be readable by non-root, as the httpd daemon does not run as root.


0

the php5.conf file in /etc/apache2/mods-enabled has a few lines at the bottom that keep php from executing inside of a user directory, so depending on your configuration, this could be your issue also. You can just comment these lines out and apache2 reload


0

If you want that http://www.mywebsite.com/ is always be sent over https you should use redirect because use mod_rewrite isn't the recommended behavior. According to Redirect Request to SSL Apache wiki page: When using SSL, you will frequently have at least two virtual hosts: one on port 80 to serve ordinary requests, and one on port 443 to serve ...


0

Normally, you should not need to create directories for logging as the loggers should take care of creating those directories automatically. Try reinstalling apache2 as a root. I am not sure about why PHP complains. Update (after reading updated question): The problem is not permissions as I doubted. It resembles with the one in here: ...


0

i have same problem xsp4 insists on running on port 8080 and i have tomcat running there. kill some other server (oracle, tomcat.. etc) that you have running on 8080 and it shall run. i really wish to get to know how to explain to xsp to run using different port within monodevelop. from command line is easy: xsp4 -port xxxx but default configs mean nothing ...


0

Here is a link of my blog post at Wordpress. It describes all general steps to setup lamp and phpMyAdmin on Ubuntu desktop. Click Here


-2

If you just need an easy web server to do local development on your system I would recommend XAMPP XAMPP is just a Lamp wrapper with a few extra features including PHP and Apache2. It also makes it really easy to use. Just follow the instructions for downloading and setting it up on your system then go to /opt/lampp directory. In that directory you will ...


0

Reading CIS Apache HTTP security I found that it suggests to add LimitExcept directive in all <Directory> directives other than the on the OS root directory. <LimitExcept GET POST OPTIONS> Require all denied </LimitExcept> This LimitExcept directive restrict unnecessary HTTP request methods, web server only accepts and processes ...


0

To solve your problem you have to setup domain name resolution. You might already have it working without knowing. Please check: Can you ping the server by it's hostname (e.g. ping example-host)? The hostname can be found easily in Ubuntu. It's the part of the prompt between the @ and the :. You should also try the same with suffixing .local → ping ...


0

If I am not mistaken, www.noip.com is a dynamic DNS provider. What this boils down to is that it allows hosts with dynamic (DHCP) IP addresses to run a small client program that updates the noip database with the current IP address of the host where the client is running. Note that this will also typically require that the IP address of your server is ...


0

Look closely at the output - there is an error in your file name. pubic_html vs. public_html This may be an error. Correct this and restart apache. Third one is not fatal, but you may want to look at ServerName variable for your virtual hosts and in global configuration file.


0

According to Apache documentation: First, all output from your CGI program must be preceded by a MIME-type header. This is HTTP header that tells the client what sort of content it is receiving. Most of the time, this will look like: Content-type: text/html Secondly, your output needs to be in HTML, or some other format that a browser ...


1

The default path to served files in Ubuntu 14.04 has changed from /var/www to /var/www/html, mainly for security reasons. The packaging has been overhauled quite significantly. /etc/apache2/conf.d/ is now /etc/apache2/conf-available/ and /etc/apache2/conf-enabled/, to match the existing sites-enabled/ and mods-enabled/ mechanisms. The simplest way to ...


0

I think it's best to check the system monitor to see what the bottleneck is. open system monitor before vagrant up and check if ram, processor or disk usage is close to max. From the images, It seems your RAM is the main bottleneck. Upgrading your RAM might help a lot.


0

sudo kill -9 <pid> Read the above comments to get more details !


0

the message error is: they say: starts The site you are trying to reach is not in default page for the moment. It may be ongoing upgrade and configuration. Try to visit this site later. If you still have problems, contact the Web site administrator.


0

First of all the IP Address you have 10.1.1.177 is private, it means that, this can only be recognized and accessible within the same domain not from the PC which is not part of your home network. So for accessing your PC from any remote site, you have to determine your Public IP address, that is, your Router's IP Address, then you have to forward your ...


2

The first problem would be because the CGI module hasn't been enabled, so Apache isn't processing anything as CGI. ENable it: sudo a2enmod cgi In Apache2.4, the configuration was cleaned up considerably, and things in the default site definition have been moved to configuration files in conf-available. Among other things, this also includes the ...


0

As the apache errors indicate, it wasn't starting because there was no /var/log/apache2/ directory due to my deleting everything in my /var/log directory while trying to debug an unrelated problem. I recreated the /var/log/apache2/ directories to get rid of the last two errors, and added 'ServerName localhost' to my /etc/apache2/apache2.conf file per these ...


0

Is the virtual machine connected to your network? if not maybe put the network setting in bridge mode. In this case the IP would be the one of the computer the virtual machine is running on. Please give more details as to what you're doing, are you making a server for your local network? Or connected to the internet? EDIT: IT says here that if you want to ...


0

In newer Ubuntu versions conf.d directory was replaced by conf-available and conf-enabled. First, make sure security.conf is enabled: sudo a2enconf security Then edit /etc/apache2/conf-enabled/security.conf and change ServerTokens OS to ServerTokens Prod.


-1

You need to completely remove mysql. Beleive me, I tryied. dpkg will not do this alone. See http://stackoverflow.com/questions/10853004/removing-mysql-5-5-completely If you are in a hurry sudo service mysql stop #or mysqld sudo killall -9 mysql sudo killall -9 mysqld sudo apt-get remove --purge mysql-server mysql-client mysql-common sudo apt-get ...


0

Try going to certificate folder and if you have .pem file, This worked for me: $ openssl x509 -in nagios.pem -noout -subject You should get something like: subject= /C=AU/ST=Australia/L=Adelaide/O=Australian web agency/CN=Your.Server.Common.Name/emailAddress=[email protected]


3

I just tested your php file in my server and it works just fine. You problem must be that the user www-data doesn't have write permissions to that folder. If indeed that user doesn't have write permissions to that folder, then you will see error messages at the file /var/log/apache2/error.log In order to look at the last errors, do tail -n 15 ...


1

I think you want to study the mod_autoindex section in the Apache documentation.


1

There is a way thanks to Gunnar Hjalmarsson! To change style Use the IndexStyleSheet directive. For example: IndexStyleSheet "/css/style.css" The /etc/apache2/sites-enabled/your_site.conf file should looks like: <VirtualHost *:80> ServerName something.com DocumentRoot /var/www/ IndexStyleSheet "/css/style.css" ... ...


1

I found the solution to my own problem. I used this guide: http://docs.joomla.org/How_to_check_if_mod_rewrite_is_enabled_on_your_server ...to find out if mod_rewrite is functioning; It was not. What this means is that the problem does NOT lie in .htaccess or your joomla settings, but in apache. If apache is not configured correctly, .htaccess will be ...


0

Find the mysql pid and kill all those child processes. You should be able to kill those child pids as follows pkill -TERM -P pid of mysql Then check if you are able to start lamp!


0

Try Below command it should stop the mysql service at your end : sudo service mysql stop Let me know if it doesn't, I can brief ahead if you have difficulties.


0

According to Apache documentation, ServerName requires an FQDN. localhost name is not a Fully qualified domain name. Try to change your 000-default.conf: <VirtualHost *:80> ServerAdmin [email protected] ServerName default.localhost DocumentRoot /var/www/ ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log ...


0

I received an answer at the Ubuntu Forums, so I'll post a summary here as well. Since I have SFTP configured properly, I was advised to remove FTP entirely and only connect via SFTP (this means uninstalling vsftpd entirely, as OpenSSH handles SFTP, not vsftpd). Doing that solved the problem of the whole filesystem being viewable via FTP. As to the problem ...


0

As like dan08 said, Apache serves files from the directory termed "Document Root". The default "Document Root" is /var/www/html. So, you have two options now. Either, Put your file into /var/www/html. Or, Change "Document Root" with the help of dan08's answer. For your case, the DocumentRoot value should be /var/www.


0

I highly doubt that you own the domain name "testing.dev" (.dev domains don't exist yet) so what is the reasoning here? Why are you using that name and how did you set it up to work locally? In order for your website to be reachable under a domain name on the internet, as opposed to a bare IP address, you need to: Register a domain name with a registry. ...


0

I did not have port 443 open on my router. I opened it, and now it works. Thanks for all of your answers.


0

Although technically this is not a question, the warning you get is a warning. Also using sudo is not required when you are root. Lastly, if you want ssl on your apache server, you should configure it.


0

Lua support in Apache in 14.04LTS is broken, see also: mod_lua is missing in 14.04? Apparently, a patch has been around for a while now, but no one has bothered shipping the fix yet. See also: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1323930, specifically - have a look at the suggested work-around.



Top 50 recent answers are included