This repository was archived by the owner on Feb 4, 2023. It is now read-only.
Little log information to perform diagnostics. #122
Unanswered
aliabianco
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I need help performing a diagnostic on a somewhat "complex" network with Fortinet APs.
I tried several examples successfully getting an ip from my dhcp network.
My ESP responds to ping.
But I don't get any response in HTTP.
There is no firewall between the devices: they are on the same local network.
The fortinet management platform tells me that there is data flow at the time of requests.
How can I get more information about the status of TCP/HTTP requests?
I already set ESPASYNC_WIFIMGR_LOGLEVEL to 4
The only example that gave me a little more information was Async_ESP_FSWebServer,
where I see the error in every request to de esp web server:
NOT_FOUND: GET http://10.17.11.207/edit
10.17.11.207 is the ip assigned via dhcp to the esp8266.
This was the best I got:
In this example I can't see the file management page (/edit)
Any suggestions on how to turn on a higher level of logging so I can get more clues to the problem?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions