so i want to try web camera of esp32-cam, the ip already showed up but when i try to open it, it can be reached
anyone know how to solve this?
I assume the ESP32-CAM is on IP 192.168.43.175 - are you attempting to connect from a different subnet?
can you ping 192.168.43.175
what is the IP address of the machine you are on?
Is your PC connected to the WiFi network produced by your ESP32-CAM? My ESP32-CAM shows up as the WiFi network "ESP32-CAM-MB"
what does it mean by trying to connect from a different subnet? sorry i'm really a newbie to this kinda thing
when i try to ping the esp32-cam IP it said destination host unreachable, i dont know why
in serial monitor it already said wifi connected, connect to the ip to connect
how to know my machine ip?
how to try to connect to the WiFi that produced by our ESP-32-CAM? i only know how to connect ESP32 to a WiFi, sorry because i'm a newbie to this kinda thing
1 Like
The same way you connect your PC to any unprotected WiFi network. You may get a warning that the WiFi you are connecting to doesn't have access. In this case, that is OK. To get back to the Internet, re-connect to your usual WiFi network.
are you on a different network to the ESP-CAM? you can have problems connecting across different subnets
on Windows run cmd (Command Prompt) and enter ipconfig, e.g.
in the above the WiFi IP address is 192.168.1.68
under linux the command is ifconfig
and after we know our machine ip
how to solve the esp32-cam web camera didnt show? please help
I'm guessing @rayharvent is using the standard CameraWebServer example that comes with the ESP32 core package. If so (he should confirm if this is true), then it doesn't produce it's own WiFi AP. It acts as a WiFi station and connects to the AP specified in the code:
// ===========================
// Enter your WiFi credentials
// ===========================
const char* ssid = "**********";
const char* password = "**********";
Start by posting your PC's IP address and submask (command is 'ipconfig' from Windows command shell). For now we'll assume that the ESP's subnet mask is 255.255.255.0.
If PC and ESP are indeed on the same subnet, then the problem may be in router's configuration. It may be set up to block comms between attached stations.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.