top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

default linux apache password

0 votes

I have a web server running on fedora. This web server is only for applicatons testing purposes. When i installed apache 2.4 it automatically create a group and an user apache.

All files/folder that are under /publi_html should have apache as user/group permissions.

This webserver runs in virtual machine and has its own IP address. Now i need to reach this webserver from a windows workstation and edit/add/delete files and folders from the public_html directory. i can not use my default user account as this account can just read files but can't edit/delete or add files/folder as standard permissions are 644 for files and 705 for folders.

i was thinking to perfom all actions (delte/move/edit...) in this public_html directory under apache account, but as apache account was installed automatically i do not have the password.

So what is the default password for apache user account ?

I guess there is better solution as on webhosting servers, you do not have apache user account, but a different one. so please, could you tell me how webhosting companies manage that (in order to reproduce a very similar way at home) ?

posted Jun 13, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

0 votes
Best answer

1) Your webserver has no reason to write to the content it serves. You should own the content and apache should read it.

2) If your operating system came with a userid named "apache", you'll have to ask them if it has a password and what it defaults to. The webserver doesn't establish it.

answer Jun 13, 2013 by anonymous
Similar Questions
+2 votes

I'm using multi ipaddress setup with virtual hosts to support different certificates.

For one of the hosts we currently don't have DNS pointing to the right IP so I edited my hosts file to point at the relevant IP. This host has a GlobalSign extended cert. We want to check the setup before going live.

On windows I checked that all the popular browsers see my extended certificate and see green url bars ok.

On linux chromium shows green, but on one machine firefox shows untrusted and on another it shows green.

Is there a way to check the certificate setup from a linux box without having the correct dns in place? I normally use GlobalSign's test stuff, but that won't work without the right dns in place.

+1 vote

Apache/Tomcat (by default) does not allow symbolic linking (nice as it can cross mounted file systems) except in the top apache/lib directory. I use hard links in the Application/WEB-INF/lib directories to reduce copying and help me manage things.

HOWEVER, some applications have special needs - e.g. pictures. You don't want to always distribute these with the release of the application (Application.war file), so symbolic links are the way to go (except for MS land, sorry). The nice solution to this is:

which must contain at least the two below lines:

However this allows ALL symbolic linking in the Application directory. I agree with the developers that this is dangerous.

Is there some way to allow linking in just ONE sub-directory of the Application?
- e.g. .../webapps/Application/images

This would allow all I need to have local images for the application without endangering other things using a symbolic link.

+1 vote

I was reading the documentation and testing out some things. We have multiple name based virtual hosts, but would like to display a page when not match is found.
According to the documentation at [] and [], the first matching servername or alias is used, with no precedence for wildcards.

What appears to be working in our case is a 'default' host with 'ServerName *', but how would I know for certain that this is the one that is always used?

Our configuration has the typical include of "/etc/httpd/conf.d/*.conf", it is here that the vhosts are defined in separate files. Should the default also be placed in here or does it have to be defined at the end of the httpd.conf (master) configuration file?

It is currently my understanding that I should place it at the bottom of httpd.conf; so to be sure it is that last that is matched, but I would like to hear from someone with more knowledge and/or experience about apache than myself. I would prefer it to be placed in the conf.d folder if possible.

Useful Links with Similar Problem
Contact Us
+91 9880187415
#470/147, 3rd Floor, 5th Main,
HSR Layout Sector 7,
Bangalore - 560102,
Karnataka INDIA.