[SOLVED] Debian (backup) server and Fedora issue

[Serophis]

Hello.

I have a NAS server with Debian installed on it which I want to use to backup my laptop which has Fedora. I'm following this guide:
http://www.debian-administration.org/articles/588

I've installed Backuppc on the server (Debian) and sudo+rsync on the client (Fedora); following the instructions down I get stuck on this part:

ssh-copy-id backuppc@192.168.1.102 (directed to the client)

Which yields this error:

No route to host

I have a router on the network: Linksys WRT54G.

I'm doing all of this through the terminal on Fedora, logging in on my server on the steps that require that.

I'm new to all of this and am basically learning as I go.

What am I doing wrong?

[PatMcLJr]

sounds like a firewall problem or you might need to do some configuring in the router

sorry, I dunno

[Serophis]

Hi, thanks for the response.

The problem persists even if I turn the router firewall off. I have noticed that the files "authorized_keys" and "known_hosts" don't appear to even exist on the server, which is strange. I have managed to manually copy the public key over to the "known_hosts" on Fedora though.

Everything seems to be working fine. I can, after all, log in to the server. I can't seem to contact myself though (through terminal, login to server (Debian), then try to login on Fedora from there), but perhaps I'm not supposed to be able to do that. I just don't know, and I can't figure it out.

Also when I try (client side):

ssh backuppc@192.168.100

and proceed to enter the password, it's not accepted (even if I know it's right). I think the public key for some reason isn't accepted.

[droidhacker]

From what I gather, the server is to be logging into the workstation via SSH in order to perform a backup. What that means is that the WORKSTATION needs to have SSHd running, and the firewall has to let port 22 through. From the SERVER, you need to be able to ssh into the workstation.

Specify the IP addresses of the server and the workstation, as well as the network address and network mask. The router is irrelevant unless it is standing between the server and the workstation.

[Serophis]

Hi, apologies for the late response.

The router is actually between my server and workstation. The server is connected through wire and the workstation through wi-fi.

The local IP addresses for the server and workstation are 192.168.1.100 and 192.168.1.102, consecutively. Subnet mask is 255.255.255.0.

[Serophis]

I have started from scratch and am stuck at the same place. I wasn't even sure what my problem really was when I started this thread, but the real problem is that I can't connect to backuppc web interface.

Through my browser, if I enter the ip to the server now, it says the following: "It works!"
However, if I try ip/backuppc, it simply 404's...

I found this thread on Google where someone says the following:

My guess would be, that you aren't pointing your browser to the right directory or need to allow acces to the directory of backuppc in your Apache2 Virtual Host Site.

Or you block your connection with your own firewall?

I suspect I'm having trouble with the "allow access" part.

Any help is greatly appreciated.

[Serophis]

Update:

I tried copying the contents of /etc/backuppc/apache.conf into /etc/apache2/sites-available/default (to the <Virtualhost></Virtualhost> container), then:

/etc/init.d/apache2 restart

Followed by:

APACHE_RUN_USER=www-data APACHE_RUN_GROUP=www-data apache2 -t

Source: http://www.howtoforge.com/forums/sho...t=23486&page=2

... and it worked! Finally, a long and arduous journey is through and another begins. I am so relieved that there are simply no words...