What is the proper way to use this alongside a previous webserver already running on port 80?

[ZongyiYang]

Hello.

If I already have a AsyncWebServer running on port 80, and I'd like to use this library to open a AP for wifi config on loss of wifi signal, what is the recommended way to run ESPAsync_WiFiManager ESPAsync_wifiManager(&server, &dnsServer)?

Normally I would provide my previous server as the input to the constructor here, but ESPAsync_wifiManager.startConfigPortal internally calls server->reset(), which would delete all my handles after it gets a new configuration.

I have found that I can comment out all instances of server->reset() to obtain the functionality I desire, but I'd prefer a more sanctioned approach if possible.

[ZongyiYang]

Nevermind, just simply calling .end() on my own server and letting this library do its thing, then calling .end() on this library's server and .begin() on my own after startConfigPortal finishes resolves my issue. I did not originally realize that I needed to .end() the server supplied to the library since it only resets the server but does not end it when it is done, which causes a conflict on port 80.