Unable to Connect Unless SSH'd

Joe_Swanson · 2024-06-22T17:13:38.473Z

I primarily use putty to SSH but if I do it through CMD I do a basic command

ssh (USER)@IP)
ssh (USER)@192.168.1.214

nextcord.errors.ApplicationInvokeError: Command raised an exception: ServerSelectionTimeoutError: 192.168.1.214:27017: timed out (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 667706b27646d3c6757e696a, topology_type: Unknown, servers: [<ServerDescription ('192.168.1.214', 27017) server_type: Unknown, rtt: None, error=NetworkTimeout('192.168.1.214:27017: timed out (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>

Jack_Woehr · 2024-06-22T17:38:34.303Z

Joe_Swanson:

The home environment is very simple. Everything in my room uses an ethernet cable with 2 basic ethernet switches.

You might try once connecting your PC and the MongoDB Raspberry Pi directly via an ethernet cable, assign them static addresses, leave out the entire rest of the network, and see if it works. Simple sanity check.

Joe_Swanson · 2024-06-22T18:43:41.511Z

Current Mongosh Log ID: 66771a73a3e25718af46b798
Connecting to:          mongodb://<credentials>@192.168.1.3:27017/?directConnection=true&appName=mongosh+2.2.5
MongoServerSelectionError: connect ETIMEDOUT 192.168.1.3:27017**strong text**

It’s something on the Pi for sure.

steevej · 2024-06-22T23:13:36.910Z

Joe_Swanson:

It’s something on the Pi for sure.

No it is not. It is something about the command you run. Your machine is

Joe_Swanson:

inet 192.168.1.214

and mongosh fails with

Joe_Swanson:

MongoServerSelectionError: connect ETIMEDOUT 192.168.1.3:27017

You are trying to connect to the wrong IP.

And it works when you ssh because you ssh to the appropriate machine

Joe_Swanson:

ssh (USER)@192.168.1.214

Joe_Swanson · 2024-06-22T23:32:56.125Z

I had to change the IP when attempting to connect to it directly, pi to PC, so both IPs are correct.

The reply above your was in response to the other guy

IP when using router
192.168.1.214

IP when going pi to pc
192.168.1.3

Jack_Woehr · 2024-06-23T00:12:30.708Z

So you’re right. Assuming your mongod config is right on the Pi (it looks right) there’s some weird networking issue in the Pi software.

Joe_Swanson · 2024-06-23T00:38:29.396Z

The config file is here

mongod.conf

Jack_Woehr · 2024-06-23T01:01:16.887Z

Right, Joe. I saw it when you first posted it. If it’s wrong about networking, I don’t see it.

Jack_Woehr · 2024-06-23T01:07:25.705Z

Joe_Swanson:

mongodb://<credentials>@192.168.1.3:27017/

Have you tried the connection with just this much of a mongdb URI?

Joe_Swanson · 2024-06-23T12:13:31.114Z

I have and it’s the same thing.

steevej · 2024-06-23T12:20:00.791Z

What OS has the PC?

Can you share the ip configuration of pc once you return to using the router?

Joe_Swanson · 2024-06-23T12:53:46.053Z

Windows 10 Home 22H2

I cannot share the IP configuration of my PC as it’s on a static IP

Jack_Woehr · 2024-06-23T14:27:50.931Z

Can you try connecting from some other client, e.g., a Linux box?

We’re doing brain surgery by telepathy here, so I’m trying to rule out your PC as the problem.

Because tens of thousands of people make this sort of connection without any issues.

steevej · 2024-06-23T15:24:29.235Z

Joe_Swanson:

I cannot share the IP configuration of my PC as it’s on a static IP

Please read IP blocks 192.168.x.x - Google Search

Your PC should have a private address in the 192.168.1.0 network just like rPi so that is can connect to your rPi. Your router most likely 192.168.1.1 does NAT over the internet, that is the address you do not want to publish. ETIMEOUT indicate network error, probably caused by IP configuration error or routing error.

Can you ping 192.168.1.214 from your PC?

Please ssh from your PC to the rPi and then share the output of

ss -tnp | grep ':22'

Also use route to tell us the route your PC takes to go to the rPi.

Joe_Swanson · 2024-06-23T21:55:28.643Z

ss -tnp | grep ':22'
ESTAB 0      0      [::ffff:192.168.1.214]:22   [::ffff:PUBLIC_IP]:53449

The PC has no private IP; it’s always a public/static IP. I can ping the pi from my PC. I’m not too entirely sure what you mean by using route; I think you mean tracert; if that’s the case, it only has 2 hops (my PC, and then it hits the Pi).

Can you try connecting from another client, e.g., a Linux box?

I can try tomorrow.

route print - windows cmd

Jack_Woehr · 2024-06-23T22:28:19.609Z

Sounds good, Joe.
Let us know.
We’re getting close, I suspect.

steevej · 2024-06-23T23:52:21.083Z

There is something fundamental you are not telling us about your network configuration and what you are trying to do.

Are you using IPv6 for your ssh?

Joe_Swanson:

The PC has no private IP

So your PC has only 1 IP address and it is directly connected and is routable from the whole internet without NAT or any port forwarding?

You need an IPv4 route from your PC to the rPI.

Joe_Swanson:

I can ping the pi from my PC.

Can you show the terminal output of this?

Like mentioned

Jack_Woehr:

tens of thousands of people make this sort of connection without any issues

so if it does not work in your case, I really suspect There is something fundamental you are not telling us about your network configuration and what you are trying to do.

Joe_Swanson · 2024-06-24T00:19:35.654Z

So your PC has only 1 IP address and is directly connected and routable from the whole internet without NAT or port forwarding?

Yes, this is why I’m replacing public IP with what it is. Nothing is hidden about the network and what I’m trying to do. I am equally confused as to why this isn’t working. I do have port forwarding on for Minecraft ports, but even then, I could connect to it briefly without the need to SSH, and I’ve got no idea what changed for it to cause that.

Pinging 192.168.1.214 with 32 bytes of data:
Reply from 192.168.1.214: bytes=32 time<1ms TTL=63
Reply from 192.168.1.214: bytes=32 time<1ms TTL=64
Reply from 192.168.1.214: bytes=32 time<1ms TTL=64
Reply from 192.168.1.214: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.214:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Joe_Swanson · 2024-06-24T11:13:59.093Z

I get the same error when using another RPI on the same OS version, Ubuntu 24.04 LTS / Noble.

Jack_Woehr · 2024-06-24T15:47:19.547Z

Okay, @Joe_Swanson , just to make sure I understand, because I’m dipping into this between meetings

The problem occurs on RPi(A) shall we call it.
The problem occurs trying to connect PC to RPi(A).
The problem still occurs connecting RPi(B) to RPi(A).

Is that correct?