Skip to main content
Right, Joe. I saw it when you first posted it. If it’s wrong about networking, I don’t see it.
Have you tried the connection with just this much of a mongdb URI?
I have and it’s the same thing.
What OS has the PC?
Can you share the ip configuration of pc once you return to using the router?
Windows 10 Home 22H2
I cannot share the IP configuration of my PC as it’s on a static IP
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.
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.
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.
Sounds good, Joe.
Let us know.
We’re getting close, I suspect.
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?
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.
Can you show the terminal output of this?
Like mentioned
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.
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
I get the same error when using another RPI on the same OS version, Ubuntu 24.04 LTS / Noble.
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?
Yes, that is correct. RPi A is also known as the DB Pi, as it will only contain the DB instance, and RPi B is known as the bot pi, as it will only contain the Discord bot.
Good, Joe … this is painful for you to debug but since we’re not in the same room or on the same network those helping you in this forum have to carefully audit what they’re looking at.
Now one last test should be the proof. Can you install MongoDB identically on the Bot Pi (RPi B) and see if that Pi exhibits the same problem when connecting from PC and from RPi A?
That works; I guess I’ll just factory reset the Pi and reconfigure MongoDB unless there may be a better solution.
I’ve factory reset the Pi, and everything is good. This also fixed my issue with the code I used on another post. I am still curious what caused this.
Could be anything from some setting you made and forgot to bit-rot on the SD card you boot from. As Dr. Seuss wrote in The 500 Hats of Bartholomew Cubbins, “People agreed it was something that just happened to happen, and wasn’t likely to happen again.” 
Closed on Jun 30, 2024
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
New & Unread Topics
| Topic | Replies | Views | Activity |
|---|---|---|---|
| Local Confluent Kafka sink to Mongo Atlas add failing | 2 | 577 | May 2024 |
| Mongodb upgrade from 4.0 to 4.2 incompatible wire version: | 6 | 946 | Jul 2024 |
| Install MongoDB Community on Windows using msiexec.exe | 1 | 221 | Aug 2024 |
| Attempting to upgrade from 3.6.23 to latest version and having issues | 0 | 59 | Aug 2024 |
| Error when trying to install mongodb-community@7.0 on macOS 11 via Homebrew | 0 | 143 | Oct 2024 |