-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot get the webgui to run #103
Comments
No. 1 yes, you can. The display is "just the output device". Connect your ESP32 to USB Power (after flashing it) and you are good to go. What do you mean by "then fixed the IP in my router"? |
Okay, that is beyond where I could help. My suggestion would be: Try DHCP first, check if the board then works fine (with the non modified code). If that works and you can access the board, maybe you can proceed from there. |
The only thing I could add here: For almost anyone it worked out of the box. Again, have you tried staying on DHCP first and check if that works? |
yep. so i resetted in the upper example all changes and left it running normally on dhcp |
Any chance to use that ESP on an another network (i.e. Hotspot of mobile)? This could maybe help to get better into the problem. |
I will close this. Feel free to open it again :) |
Hi there,
hope u guys can help me. I do have multiple questions.
I basically uploaded the standard configuration, connected through Wifi and setup the AP settings. Which worked fine, then fixed the IP in my router. When I try to ping or open the IP in the web browser I am not able to reach it though.
So I tried to setup the IP also in code, for example in frontend/.env (which should only matter when actually making a request I think). Then I tried setting up the static ip config in constants.h. But it will still not work.
I also tried to debug but then I get an error that states that there is not enough flash memory for it.
Also even after uploading an esp32 image again the AP settings seem to be stored. How am I able to delete them?
The text was updated successfully, but these errors were encountered: