server not reachable after calling end() and begin().

[mkalkbrenner]

• Which board: ESP32S3

AsyncWebServer *server = new AsyncWebServer(80);
// Start the web server
server->begin();

delay(10000);
server->end();

delay(10000);
server->begin();

The server works fine. But if I stop the sever and start it again later, it isn't reachable anymore.

[mkalkbrenner]

Some more tests.
Even that doesn't work:

AsyncWebServer *server = new AsyncWebServer(80);
// Start the web server
server->begin();

delay(10000);
server->end();
delete server;
server = nullptr;

delay(10000);
server = new AsyncWebServer(80);
server->begin();

The server is not reachable on port 80 after the "restart".

But if I do this, I can reach the server on port 81:

AsyncWebServer *server = new AsyncWebServer(80);
// Start the web server
server->begin();

delay(10000);
server->end();
delete server;
server = nullptr;

delay(10000);
server = new AsyncWebServer(81);
server->begin();

[mathieucarbou]

I can reproduce indeed. Ahah! I didn't have my WiFi Client activated :P

So I cannot reproduce.

you can add at the end of the SimpleServer:

  Serial.println("begin()");
  server.begin();

  delay(10000);
  Serial.println("end()");
  server.end();
  delay(10000);
  Serial.println("begin()");
  server.begin();

• wait for begin()
• do a curl requests curl -v http://192.168.4.1
• wait for end(), then begin()
• do a curl request curl -v http://192.168.4.1

begin()
* Connection from 192.168.4.2:58749
> GET / HTTP/1.1
> Host: 192.168.4.1
> User-Agent: curl/8.11.1
> Accept: */*
>
* Processed in 1 ms
< HTTP/1.1 200 OK
< connection: close
<
end()
begin()
=========== After Setup Start ============
INTERNAL Memory Info:
------------------------------------------
  Total Size        :   326716 B ( 319.1 KB)
  Free Bytes        :   219248 B ( 214.1 KB)
  Allocated Bytes   :    95436 B (  93.2 KB)
  Minimum Free Bytes:   197212 B ( 192.6 KB)
  Largest Free Block:   110580 B ( 108.0 KB)
------------------------------------------
GPIO Info:
------------------------------------------
  GPIO : BUS_TYPE[bus/unit][chan]
  --------------------------------------  
     1 : UART_TX[0]
     3 : UART_RX[0]
     4 : GPIO
============ After Setup End =============
Free heap: 219248
Free heap: 219248
* Connection from 192.168.4.2:58794
> GET / HTTP/1.1
> Host: 192.168.4.1
> User-Agent: curl/8.11.1
> Accept: */*
>
* Processed in 2 ms
< HTTP/1.1 200 OK
< connection: close
<
Free heap: 219248
Free heap: 219248

I will move to a discussion until it can be proven there is an issue, or until you found what is wrong on your setup.

• Maybe post a complete ino file to reproduce.
• Also, please test with the SimpleServer example
• Verify your libraries

Note: there is an issue template we have written specifically to know about the environment

Please answer all questions before opening an issue next time, or open a discussion...

[mkalkbrenner]

Thanks for your quick reply.

Basically I did exactly what you described as test case.

Can you share your ino file so that I do exactly the same?

BTW the error happens in the ZeDMD project that I recently switched to pioarduino:

[env:S3-N16R8_256x64]
framework = arduino
platform = https://github.com/pioarduino/platform-espressif32/releases/download/stable/platform-espressif32.zip
board = esp32-s3-wroom-1-n16r8
board_build.partitions = partitions_16MB.csv
board_build.filesystem = littlefs
lib_deps =
    https://github.com/mrfaptastic/ESP32-HUB75-MatrixPanel-DMA#3.0.11
    thomasfredericks/Bounce2
    https://github.com/ESP32Async/AsyncTCP#v3.3.2
    https://github.com/ESP32Async/ESPAsyncWebServer#v3.6.0
build_flags =
    -DNO_GFX=1
    -DZEDMD_HD=1
    -DDISPLAY_LED_MATRIX=1
    -DPIXEL_COLOR_DEPTH_BITS=8
    -DNO_FAST_FUNCTIONS=1
    -DMINIZ_NO_STDIO=1
    -DMINIZ_NO_TIME=1
    -DMINIZ_NO_DEFLATE_APIS=1
    -DMINIZ_NO_ARCHIVE_APIS=1
    -DMINIZ_NO_ZLIB_COMPATIBLE_NAMES=1
    -DCONFIG_ASYNC_TCP_RUNNING_CORE=0
    -DCONFIG_ASYNC_TCP_STACK_SIZE=4096
    -DARDUINO_EVENT_RUNNING_CORE=0
    -Os
build_unflags = -Og

https://github.com/PPUC/ZeDMD

[mathieucarbou]

Can you share your ino file so that I do exactly the same?

I've used the SimpleServer.ino from this project with the modifications described above...

Though the params are:

  -D CONFIG_ASYNC_TCP_MAX_ACK_TIME=5000
  -D CONFIG_ASYNC_TCP_PRIORITY=10
  -D CONFIG_ASYNC_TCP_QUEUE_SIZE=64
  -D CONFIG_ASYNC_TCP_RUNNING_CORE=1
  -D CONFIG_ASYNC_TCP_STACK_SIZE=4096

but these should not impact.

we are using pioarduino also:

platform = https://github.com/pioarduino/platform-espressif32/releases/download/53.03.11/platform-espressif32.zip

that's really strange!

[mathieucarbou]

https://github.com/PPUC/ZeDMD/blob/a27fdd53eff87601abfb439af8544d6333a455a5/src/main.cpp#L1297-L1311

I have an application also with both AsyncTCP (ESPAsyncWS) on websocket and AsyncUDP.

And I sometimes see some issues reaching the web server and I found that this was because of AsyncUDP.

Try running your async_tcp task on core 1:

-D CONFIG_ASYNC_TCP_RUNNING_CORE=1

CONFIG_ARDUINO_UDP_TASK_PRIORITY is 3 and CONFIG_ARDUINO_UDP_RUNNING_CORE is 0. fyi.

[mkalkbrenner]

Sorry for the delay.

I experimented a bit more. And it seems that websever has issues to be "started" after the ESP32 S3 is already running for more than 30 seconds. Actually it starts, but it takes very long until a client gets a response, about one minute.
That requires further investigation.
But I will update to 3.6.2 first.

[mathieucarbou]

• did you try disable the UDP task ?
• did you try to isolate the issue by working on a minimal reproductible use case without your app stuff ?
• did you try to reproduce with the examples in the project?
• did you try with -DCONFIG_ASYNC_TCP_RUNNING_CORE=1 ?