Unable to Connect Unless SSH'd

Jack_Woehr · 2024-06-22T02:40:44.786Z

Well, something is blocking you. What’s the environment you’re connecting from? Corporate? Your corporate firewall could be forbidding access to “strange” ports.

steevej · 2024-06-22T15:30:36.751Z

Share the output of the following commands:

ss -tlnp
ip addr list
ps -aef | grep [m]ongo

Joe_Swanson · 2024-06-22T16:03:50.560Z

It’s a home environment; it runs on the same network with 0 firewall settings anywhere.

I’m able to SSH into the Pi just fine,

user@ubuntu:~$ ss -tlnp
State   Recv-Q   Send-Q     Local Address:Port      Peer Address:Port  Process
LISTEN  0        4096             0.0.0.0:27017          0.0.0.0:*
LISTEN  0        4096       127.0.0.53%lo:53             0.0.0.0:*
LISTEN  0        4096          127.0.0.54:53             0.0.0.0:*
LISTEN  0        4096                   *:22                   *:*

user@ubuntu:~$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:2e:a5:1e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.214/24 metric 100 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 54718sec preferred_lft 54718sec
    inet6 fe80::2ecf:67ff:fe2e:a51e/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 2c:cf:67:2e:a5:1f brd ff:ff:ff:ff:ff:ff

user@ubuntu:~$ ps -aef | grep [m]ongo
mongodb      885       1  0 Jun20 ?        00:11:16 /usr/bin/mongod --config /etc/mongod.conf

Jack_Woehr · 2024-06-22T16:11:15.092Z

How does your home environment work?
Looks like you’re using DHCP … is the DHCP server your ISP’s network device?
Have you checked the firewall settings in that device?

Joe_Swanson · 2024-06-22T16:25:12.823Z

Yes, it is that, and there are no firewall settings configured. I’ve only done port forwarding, but that’s to my PC, and it’s a very simple/straightforward thing.

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

steevej · 2024-06-22T17:01:17.873Z

share the value of IP and PORT you used to get the ETIMEOUT you got in the hastebin of the original post.

share the command you use to ssh to the rpi.

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.