Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have rented a Debian server using gandi.net. I linked the server to a domain name. When I go on the web on my_domain_name.com, I get :
It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.
This proves that apache2 is running, right? So the question is where do I add content?
In /home/username/ or where ?
I'm trying to run some index.php file and I don't know where to put it in order to run it. What's the path?
The default document root for apache2 is /var/www but that can be reconfigured if necessary.
To be sure that Apache is indeed running you can type:
ps -ef | grep apache
If this line of terminal code does not return something Apache is not running. If it returns something it is.
Good luck with your web server.
Apache has a default directory in somewhere like /var/www, but you can configure it to serve content in other directories. See Apache DocumentRoot
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have an apache server running Apache/mod_php.
On Fresh start and when using sudo service apache2 restart the correct php.ini file is loaded:
Doing a graceful reload of apache i.e "sudo service apache2 graceful" results in php loading a different php.ini (which is non-existing on filesystem):
What could be causing this and any ideas on how to resolve it?
From http://php.net/php.ini:
Note:
The Apache web server changes the directory to root at startup, causing PHP to attempt to read php.ini from the root filesystem if it exists.
Are you sure /php.ini does not exist?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I follow this guide to install LAMP server on fedora 22 workstation
How To Install LAMP Stack (Apache, MariaDB And PHP) In Fedora 22
Everything working well except phpmyadmin.
When i need access it of the browser
i see nothing (blank page)
How i can fix this issue ?
Any Suggestions ?
Possibly you can get more info via 2 things
1- Enabling php display_errors in php.ini file which you can find by running
php --ini
changing display_errors to on and save it then restart apache web server and revisit phpmyadmin url which should show you the error
2- looking in apache error log which mostly located in /var/log/httpd/error.log
you can use tail -f for better tshooting
tail -f /var/log/httpd/error.log
Try running phpMyAdmin's index.php over the command line. This should give you more information about the error that causes the problem.
php index.php
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
Much as the title says, I'm hosting a PHP application in an EC2 instance (elastic beanstalk) on Amazon Web Services, actually running Wordpress connecting to an RDS instance. I've been needing to restart apache for a number of reasons, mainly because I'm using the mod_pagespeed apache module.
Almost without fail when I do that though, it deletes the contents of /var/www/html/ using this command:
sudo service httpd restart
I'm at a bit of a loss since I'm new to AWS, but this clearly isn't desired functionality. Is there another way I ought to go about restarting apache? Can anyone explain why that's happening?
Any advice welcomed, I feel I've got to grips well with most of the admin but this is just a head scratcher for me!
I'm not sure what's happening with the deleting of the content, but you can try to use the graceful command to restart instead.
sudo apache2ctl graceful
This will gracefully reload its configuration!
or the reload command
sudo service httpd reload
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
As client requirement i need to remove the suexec from apache to remove vulnerabilties.
To do that i am using apachectl -V command on linux machine.
i am getting many variables with path of the file like
-D SUEXEC_BIN="/usr/sbin/suexec"
From the documentation on apache.org
if i would remove or rename this suexec file from the above path and restart the server, suexec will be deactivated and the above variable won't be show the file.
I am doing the same but the reflection is not showing. please help me out this.
The -D SUEXEC_BIN=… text that you're seeing is an option that was specified when the web server was compiled. It doesn't mean that suexec is being used, and it can't be removed without recompiling the web server (which you should not do here).
Refer to manual on how to disable or enable suexec: http://httpd.apache.org/docs/2.2/suexec.html#enable
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I was wondering why my system says it is running the php from the /etc/php5/apache2/php.ini
directory when in fact it was running it from the /etc/php5/cli/php.ini .
When I did a phpinfo() on a file in the directory of the folder, I received this however the changes to the configuration file wasn't impacting the server until I searched the whole system for a php.ini file and found the php.ini file under the cli/ directory:
Hopefully you can see it. I wasn't sure exactly how to put in onto SO.
it's intentional so you can easily have different configuration depending on your runtime environment.
In your environment when php runs in command line mode it uses /etc/php5/cli/php.ini.
When you access it from browser php is running from apache. So then /etc/php5/apache2/php.ini is used.