Unable to access web UI nor SSH - Network timeout

482 views
Skip to first unread message

Dad4 Service

unread,
Dec 18, 2021, 7:47:17 AM12/18/21
to motioneye
I just setup an "OctoCam" from Pimoroni using motionEyeOS and am able to boot w/out issue. It connects to my wifi and I can SSH out of the octocam but not into it. That is it has outbound connections no problem but when I attempt to ssh or 192.168.1.13 in browser into it the connection times out. Also if I try pinging the octocam (Raspberry Pi zero w) the connection times out. The ssh out is to a remote computer on WAN (don't have a LAN ssh enabled comp).

I've attempted help from pimoroni and adafruit but they don't know the os well enough. Anyone here have any ideas?

StarbaseSSD

unread,
Dec 18, 2021, 7:54:28 AM12/18/21
to motioneye
Did you enable SSH (at boot via a file called ssh or ssh.txt in the /boot partition) or in the WebGUI? It is disabled by default.

StarbaseSSD

unread,
Dec 18, 2021, 8:29:50 AM12/18/21
to motioneye
Looking at it after a bit of java, How does it get it's IP address information? If you are in with a keyboard and monitor, what does the command
ip a
get you?

Dad4 Service

unread,
Dec 18, 2021, 4:43:50 PM12/18/21
to motioneye
Yes, I enabled SSH using just a blank file in the boot directory named ssh. Also manually started ssh just in case (don't remember the command but was getting help).

Not sure what "Looking at it after a bit of java" means but guessing you meant that you had been looking at it and then go on to ask me a the question. The IP is provided via DHCP from router wirelessly through the conf file:  wpa_supplicant.conf also put in the boot dir. See these instructions: https://learn.pimoroni.com/article/motioneye-os-on-your-octocam

Finely, haven't done the ip a command yet, but did ifconfig and it appeared to be all correct. Here's a photo of what it shows:
20211218_030622.jpg

The quality of the monitor is low so I can't read it all too easily. But the IP is clear enough 192.168.1.13.

I'm considering doing another build of linux and having a go at installing motioneye. I kinda like the idea of having more functionality on the device anyway. Any suggestions for that? Though I would still like help getting it working with just motioneyeOS.

StarbaseSSD

unread,
Dec 18, 2021, 5:02:22 PM12/18/21
to motioneye
The java reference was to lack of coffee prior to the first reply. (attempt at humor. I failed miserably)
What are you trying to SSH or Web into it from? PC or tablet or phone or something else?
What is the IP address of that device?

As to alternatives, there are several instructional sections for installing on RaspberryPiOS (recommended) and other OSs (not so recommended due to lack of RAM on PiZeroW). I would use Legacy Lite, and follow these instructions:
https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian
If you feel the need to give up on motionEyeOS.
BTW, if you are using motionEyeOS, be sure to try dev20201026, not 20200606.
It is much more stable for most uses.

Dad4 Service

unread,
Dec 18, 2021, 6:05:36 PM12/18/21
to motioneye
Sorry not a java drinker, I get it now :) I tied 2 windows comps (win 7 and win 10) and even tried from remote WAN terminal ... Used SSH out from the pi to my remote linux server then attempted to ssh back to the pi from that (opened port but didn't help) Oh also attempted just web ui from phone and browsers on pc's.

All pings from the pi will go out to other devices but with high latency time as in 200ms but any incoming connections to the pi are failing with timeout. When I attempt to ping from pc to pc or to router from pc all times are <10ms usually <1ms.
so the IP's of all the devices are 192.168.1.x pi is .13 pc1 is .3 and pc2 is .(i forgot but is in same LAN)
I'll check out the 20201026 build :) thanks for that! Gotta redo the install. Though I'll probably use another sd card just so I can keep working on the first one to see what's happened.

StarbaseSSD

unread,
Dec 18, 2021, 6:12:00 PM12/18/21
to motioneye
Next silly question:
Do you have anything else on the same WiFi as the OctoCam? If yes, can you ping it from the PCs?
I'm curious if you can get to anything on the Wifi from the PCs.  Possible routing issue, or firewall, as some WiFi Access Points prevent traffic to devices/between devices, especially Mesh APs and WifI extenders.

StarbaseSSD

unread,
Dec 18, 2021, 6:16:27 PM12/18/21
to motioneye
As a test of the last, on either the Win7 or Win10 PCs, can you open a command line window and run the command
tracert 192.168.1.13
Which is traceroute to the OctoCam
This might be helpful.

Dad4 Service

unread,
Dec 18, 2021, 6:23:06 PM12/18/21
to motioneye
Ah! Good idea, note pinging the router from the OctoCam was 200+ms average ... That tracert will have to be later I need more sleep (didn't sleep but 1hr today)

I only have router>PC, router>PC, oh!!! And router>printer. Both pc's can access the printer as well. other than 2 phones and the pi all others are hardwired.
1 router, 2 pc's, 1 printer, 2 mobile phones, 1 pi (got 3 pi's actually but just staring with one)
Very simple home network.

With the build you suggested, should I still create the files: wpa_supplicant.conf and ssh with the suggested info on the https://learn.pimoroni.com/article/motioneye-os-on-your-octocam site? (I suspect yes)

StarbaseSSD

unread,
Dec 18, 2021, 6:30:58 PM12/18/21
to motioneye
" With the build you suggested, should I still create the files: wpa_supplicant.conf and ssh with the suggested info on the https://learn.pimoroni.com/article/motioneye-os-on-your-octocam site? (I suspect yes) "
The answer is Yes, same setup capability.

Dad4 Service

unread,
Dec 18, 2021, 6:54:40 PM12/18/21
to motioneye
So i just tried it w/out limbs (no keyboard or mouse) but with head and could see it got same IP (same mac so makes since) even with new SD/build ... Unable to ping ... Getting:

C:\Users\sysadmin>ping 192.168.1.13

Pinging 192.168.1.13 with 32 bytes of data:
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.

Ping statistics for 192.168.1.13:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I run a "hosts" file so that might be related ... gonna check that now.
Just set hosts to simple (only localhost) - didn't help. Gonna reboot pc to see if that helps.

StarbaseSSD

unread,
Dec 18, 2021, 7:08:34 PM12/18/21
to motioneye
Please run the tracert command from either PC:
tracert 192.168.2.13


Dad4 Service

unread,
Dec 18, 2021, 7:16:38 PM12/18/21
to motioneye
reboot and did so ... 
C:\Users\sysadmin>tracert 192.168.1.13

Tracing route to 192.168.1.13 over a maximum of 30 hops

  1  sysadmin-PC [192.168.1.3]  reports: Destination host unreachable.

Trace complete.

also tried from other and got same: 

C:\Users\tlcom>tracert 192.168.1.13

Tracing route to 192.168.1.13 over a maximum of 30 hops

  1  Grandma-s [192.168.1.4]  reports: Destination host unreachable.

Trace complete.

StarbaseSSD

unread,
Dec 18, 2021, 7:26:14 PM12/18/21
to motioneye
Well, there is no route to the OctoCam. This points to a Firewall on the WiFi Access Point, or no route through the Access Point to the WiFi devices.
Question becomes why.
Is the WiFi Access Point part of your modem/router?
Are you using a WiFi Extender? Or a WiFi mesh?
Can you tracert to a phone on the WiFi?
It's be interesting to try another Pi/RPiOS to see if you can see it... But I doubt you will be able to.
If you have monitor & keyboard attached to the OctoCam, I would run:
traceroute 192.168.2.3
(one of the PCs and the Windows command is slightly different) and see what it says...




Dad4 Service

unread,
Dec 18, 2021, 7:46:46 PM12/18/21
to motioneye
see attached for three photos of the boot and ip a and traceroute 192.168.1.3 - scratch that ... Just the traceroute 192.168.1.3 and .1 ... It's blocked in the router. 

The WiFi Access Point is my router Netgear R6400v2 ... Modem is separate. 
No WiFi Extender. Don't know what a WiFi mesh is.
tracert to phone: 
C:\Users\sysadmin>tracert 192.168.1.9

Tracing route to 192.168.1.9 over a maximum of 30 hops


  1  sysadmin-PC [192.168.1.3]  reports: Destination host unreachable.

Trace complete.

Now I gotta figure out where in the router the issue is ... It seems windows to windows no issue but windows to linux and back has issue.
20211218_164010.jpg

StarbaseSSD

unread,
Dec 18, 2021, 8:09:40 PM12/18/21
to motioneye
Movie night with the grandkids, will look at your setup more in the morning. I have a Netgear NighthawkNighthawk X6 R8000 and had to set mine to Access Point mode to get it to work correctly with the rest of my network (Ubiquity Router, and Cisco Switches, Arris Modem, etc)
I'll let you know in the morning.

StarbaseSSD

unread,
Dec 18, 2021, 8:10:37 PM12/18/21
to motioneye
BTW, it's not a Win to Linux issue, it's a Wired to wireless issue...

Dad4 Service

unread,
Dec 18, 2021, 8:17:39 PM12/18/21
to motioneye
So I found this setting: Disable IGMP Proxying in the WAN setup ... It was checked ... I unchecked it. Performed another tracert to 192.168.1.13 from pc ... HAZA!!! Worked.

Dad4 Service

unread,
Dec 18, 2021, 8:22:03 PM12/18/21
to motioneye
I read this article and felt ... Hey that sounds right and related ... so I unchecked "Disable IGMP Proxying" found in the WAN setup on my Netgear R6400v2 (sorry I'm repeating all this) but It was the solution.

Dad4 Service

unread,
Dec 19, 2021, 3:45:01 AM12/19/21
to motioneye
Turns out it was probably not the IGMP setting but simply rebooting the router(that setting caused a reboot). I had trouble connecting to some websites after the change so I reboot the router again and found there was was no internet. Set the IGMP back to disabled and reboot the modem ... Now all is working ... f'ing router ... It was higher end model than I usually get and it's been more trouble!!!

Thanks for your help StarbaseSSD.

Dewey3

unread,
Dec 19, 2021, 7:20:32 AM12/19/21
to motioneye
Very interesting.  I've been watching this thread because we have been having connection problems for the last couple months that appear to be getting progressively worse.  I never chimed in because it has not affected any of my cameras (MotionEyeOS), but it has certainly affected our PC's.  I've done all of the process of elimination that I could, and have not ruled out that either Micro$oft pushed out an update that affected our wifi connectivity, or that the internet has become so busy during this pandemic, that at times, it's just one big denial of service.  During my process of elimination, I switched my current Netgear R8000P for my previous R7000P, and that didn't make anything better; however, every time I would reboot the whole house internet (Netgear cable modem AND router, Comcast ISP), things would work better for a few hours then the trouble would return.  It go so bad yesterday that I started working off of my M2000 hotspot (T-Mobile), and was surprised when I started having the same problems - telling me it couldn't have had anything to do with our connectivity equipment or ISP.

The problems we're experiencing and reason I've been watching this thread:
- Google and Firefox browsers returning that the website was not found, but then automatically refreshing and working 2-4 seconds later
- Multiple attempts required to reach some sites, mostly FTP but HTTP/S also before the connection would be made rather than returning that the site is unreachable
- Zero byte download files when using Firefox, and occasional failed downloads when using Chrome
- Software applications not executing properly because they are unable to reach their programmed sites (most FTP) ... I have also seen this when running things on my RPis in Linux
- Clicking on links in other applications (Micro$oft Access in my case) returning that they are not able to go out on the internet

Again, while my MotionEyeOS cameras appear to be working well from behind and outside the home internet, I am still having some of the problems as reported here, so with all that said, is the problem reported here really MotionEye, or something else that is appearing in MotionEye ???

Sorry for the rant,
Dewey

--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/94aaac1a-bdfb-4a85-a495-01187fab8812n%40googlegroups.com.

StarbaseSSD

unread,
Dec 19, 2021, 8:13:32 AM12/19/21
to motioneye
Glad to hear you got it resolved. If I may suggest, if it seems to come back, consider turning all the advanced functions off, and turn off the guest services and just make it an Access Point.
Good Luck...

StarbaseSSD

unread,
Dec 19, 2021, 8:25:14 AM12/19/21
to motioneye
@dewey:
I mentioned that I had to change over my Nighthawk X6 R8000 to Access Point. I also disabled all my "Guest" functionality to Off, and turned off a bunch of 'advanced' options to get it to work correctly. I also had to update firmware a few times. Currently: Firmware Version V1.0.4.76_10.1.82and seems to be fairly stable. I have 35 devices connected, and have up to 60 regularly connecting. It's a decent router, but like others say about it, maybe a few too many features. Without all the 'fun stuff' it gives me decent coverage and speed. I like the fact you can install DD-WRT firmware, too, and may do it when I get a new WiFi router down the road.

Dewey3

unread,
Dec 19, 2021, 9:19:25 AM12/19/21
to motioneye
Thanks for the tips Keven while I also don't like or use all the "features" like QOS, Guest, and Traffic Meter either, we may have different equipment.  My 8000 has the P suffix and is on the latest V1.4.2.84_1.3.42 firmware.  The eye opener for me was when I started getting the same problems on the hotspot which has nothing to do with the house equipment or ISP.  I still appreciate your tips and thank you again.

Dewey

Reply all
Reply to author
Forward
0 new messages