Cannot contact Debian Server anymore thru SSH and traceroute

G

GringoMG

New Member
Joined
Jan 15, 2024
Messages
3
Reaction score
4
Credits
52
Hi,
My name is Jos and I am from the Netherlands.
I have a pet shop in a village 10 km from my home.
In my pet-shop there are 2 terminals with an open source POS system.
These 2 terminals are serviced be a HP Proliant mini server with a Debian Wheezy OS, apache server.

Until Dec. 15 2023 I could enter the Debian Server through ssh.
on Dec 15 we discovered a mice nest on the router. we cleaned the router and internet worked ok again.
Here is the command that was successful tot connect:
jbrik@dell5591:~$ ssh -vvv [email protected] -p X00XX
After that I could enter the root password and was able to execute commands in the terminal of the server.

Also every night the server was back-upped to a home backup server. Worked flawless until the 15th of December 23.
After Dec. 15 I could not reach the server anymore and the daily backup stopped.

Here is the output of triple verbose ssh command:
jbrik@dell5591:~$ ssh -vvv [email protected] -p X00XX
OpenSSH_8.4p1 Debian-5+deb11u3, OpenSSL 1.1.1w 11 Sep 2023
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname XX.XX.113.176 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/jbrik/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/jbrik/.ssh/known_hosts2'
debug2: ssh_connect_direct
debug1: Connecting to XX.XX.113.176 [XX.XX.113.176] port X00XX.
debug1: connect to address XX.XX.113.176 port X00XX: Connection timed out
ssh: connect to host XX.XX.113.176 port X00XX: Connection timed out

Here is the output of traceroute:
jbrik@dell5591:~$ traceroute XX.XX.113.176
traceroute to XX.XX.113.176 (XX.XX.113.176), 30 hops max, 60 byte packets
1 fritz.box (XXX.168.188.1) 11.678 ms 11.581 ms 11.527 ms
2 home (XXX.168.1.1) 12.553 ms 12.503 ms 12.454 ms
3 1-204-177-143.ftth.glasoperator.nl (143.177.204.1) 12.067 ms 12.598 ms 12.549 ms
4 10.10.13.45 (10.10.13.45) 20.259 ms 10.10.15.45 (10.10.15.45) 20.209 ms 20.160 ms
5 10.10.12.61 (10.10.12.61) 20.110 ms 21.008 ms 21.146 ms
6 10.226.4.6 (10.226.4.6) 21.121 ms 10.226.4.3 (10.226.4.3) 12.730 ms 10.226.4.6 (10.226.4.6) 13.321 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 *^C

Ich checked the following:
ssh server is running both on laptop (Distro: LMDE 5 Elsie base: Debian 11.2 bullseye ) and Debian server. Ssh was running on both.

I set back the factory defaults in the TP link Router Model: TL-WR1043ND and restored the essential parameters with the help of screenshots. I made sure that port X00XX was configured correctly.
I restarted the Frizbox router at my home.

I appreciate any help to restore entering the Debian server and restoring the daily backup function again.
 


Without being able to help directly on the problem, perhaps consider upgrading the releases. Debian wheezy was released in 2013 and now considered "obsolete", and bullseye, now considered "oldstable", has been upgraded to bookworm. The changelogs on openssh over the last years are very extensive making the functioning in bookworm likely to be quite a bit more robust than a release that is 10 years older. When I read anything on ssh development, there's usually a comment such as: "the importance of regularly updating and patching security software and protocols." Sorry I can't be of any real help with your current set up.
 
Thank you for your reply.
I considered that and discussed that with people on the Debian fora. Decided for no upgrade because it would involve a complete redesign of the open source POS application in PHP and Mysql with transfer ande merge problems.
Copying/imaging/ mirroring of the current system is a problem because of the HP Proliant server that has RAID.
The problem can be ssh but ping and traceroute are not working either, so I guess it must be a network issue.
So I appreciate any idea to debug and analyse this issue.
I am looking for a solution within the current configuration.
 
Still feeling rather unhelpful, nevertheless, these thoughts come to mind.

In the past when getting the message "network is unreachable", or similar, the first step I usually take is to check the hardware, all the sockets involved which can be ethernet, usb, wifi dongle location, router connectivity etc. I imagine you may have done that, even a few times.

Given that ssh, ping and traceroute all fail, the problem appears to be at a lower level than applications. Presumably configurations in the apps involved haven't changed, so one may think there's no issue there. Intuitively it feels like a hardware issue, but I simply cannot say.

Is it possible to actually restart the whole system, for example, restart all the computers and routers so they all have to re-read their configs. That has worked here at times, but not always.

Resetting the routers to factory settings and rebooting has worked on occasions here.
That's about it for the moment.
 
"Is it possible to actually restart the whole system, for example, restart all the computers and routers so they all have to re-read their configs. That has worked here at times, but not always.

Resetting the routers to factory settings and rebooting has worked on occasions here."

I had done that all before posting.
Thanks again for your willingness to help.
 
GringoMG said:
10.226.4.6 (10.226.4.6) 13.321 ms
Click to expand...
I would check the system of the hop on the last system where you get a reaction, if that is not the same system as the one that was cleaned then maybe another router broke?
 
Smells like a
1) Firewall
2) Timeout
3) fail2ban
3) faulty sshd_config

Many VPS Providers have a VNC session, that you can access for troubleshooting. Check out above mentioned
 
You must log in or register to reply here.

Staff online

Members online

Total: 506 (members: 6, guests: 500)

Latest posts

Top