Latest Announcemnent
New thread
Status
Not open for further replies.
22 comments
you have to alter settings in httpd.conf

You can change ever path that says /var/www/ to /home/

to know the exact path of httpd.conf in your OS use this command in ssh

Code: 
find / -name httpd.conf
this would show you path of every httpd.conf file in ur file system
 
You can enter this in your terminal/console/ssh...
Change username to the actual username!
Code: 
sudo cp -R /var/www/ /home/username/
sudo chown -R username:username /home/username/www/
sudo rm -r /var/www/
sudo ln -s /home/username/www /var/www

.. Ok I'm joking.

Do this :)
Code: 
sudo nano /etc/apache2/sites-enabled/default
Look for /var/www/ and replace it to what you want.
Pro-tip: /var/www/ might occur multiple times, make sure to change ALL /var/www's
Pro-tip²: when you're done, make sure to restart apache.
Code: 
sudo /etc/init.d/apache2 restart

edit:
to all those saying edit httpd.conf.
In debian httpd.conf is named apache2.conf
In debian all the virtualhost-shit isn't set in apache2.conf but placed in /etc/apache2/sites-enabled/ ( actually /sites-available and linked to sites-enabled )
This ofcourse if the apache2 package got installed using the package manager.
 
Last edited:
Yes, but you should have root access, so just fire up putty ( google it ) and connect to your server like a boss.

I can't help you further if you can't connect using SSH.
Perhaps someone else can take it from here.

EDIT:
Checked your screenshot.
You have SSH, good. Now just do what I said.
If ISP CONFIG crashes due to what you're going to do, you'll have killed two birds with one stone!
 
Robin H said:
Yes, but you should have root access, so just fire up putty ( google it ) and connect to your server like a boss.

I can't help you further if you can't connect using SSH.
Perhaps someone else can take it from here.

EDIT:
Checked your screenshot.
You have SSH, good. Now just do what I said.
If ISP CONFIG crashes due to what you're going to do, you'll have killed two birds with one stone!
Click to expand...


is blank :(

screen http://www.filpic.eu/di-UZ75.png
 
ssh console

root@vps-176-31-91-37:~# ls -l /etc/apache2/sites-enabled/
total 0
lrwxrwxrwx 1 root root 39 Jun 5 17:58 000-apps.vhost -> /etc/apache2/sites-available/apps.vhost
lrwxrwxrwx 1 root root 26 Jun 5 17:18 000-default -> ../sites-available/default
lrwxrwxrwx 1 root root 43 Jun 5 17:58 000-ispconfig.conf -> /etc/apache2/sites-available/ispconfig.conf
lrwxrwxrwx 1 root root 44 Jun 5 17:59 000-ispconfig.vhost -> /etc/apache2/sites-available/ispconfig.vhost
lrwxrwxrwx 1 root root 47 Jun 5 18:02 100-176.31.91.37.vhost -> /etc/apache2/sites-available/176.31.91.37.vhost
lrwxrwxrwx 1 root root 45 Jun 5 20:38 100-conrado.pl.vhost -> /etc/apache2/sites-available/conrado.pl.vhost
lrwxrwxrwx 1 root root 47 Jun 5 20:43 100-conradock.pl.vhost -> /etc/apache2/sites-available/conradock.pl.vhost
lrwxrwxrwx 1 root root 47 Jun 5 20:48 100-discomuza****.vhost -> /etc/apache2/sites-available/discomuza****.vhost
lrwxrwxrwx 1 root root 44 Jun 5 20:59 100-games.net.vhost -> /etc/apache2/sites-available/games.net.vhost
lrwxrwxrwx 1 root root 43 Jun 5 19:19 100-mnhnb****.vhost -> /etc/apache2/sites-available/mnhnb****.vhost
lrwxrwxrwx 1 root root 44 Jun 5 20:18 100-mywiiu.pl.vhost -> /etc/apache2/sites-available/mywiiu.pl.vhost
lrwxrwxrwx 1 root root 44 Jun 5 21:08 100-qames.net.vhost -> /etc/apache2/sites-available/qames.net.vhost
lrwxrwxrwx 1 root root 48 Jun 5 19:16 100-testujemy2****.vhost -> /etc/apache2/sites-available/testujemy2****.vhost
root@vps-176-31-91-37:~#
Click to expand...
 
There you go.
You can check all the .vhost files.

Your best bet is 000-ispconfig.vhost

Code: 
nano /etc/apache2/sites-enabled/000-ispconfig.vhost

or 176.31.91.37.vhost

Code: 
nano /etc/apache2/sites-enabled/176.31.91.37.vhost
 
Look for /var/www/ and edit it. It might occur more than once.
When saved make sure you restart apache.

Code: 
/etc/init.d/apache2 restart
 
Status
Not open for further replies.
Back
Top