Sorry to hear that.
The output of the connectivity log is not the same thing as the Authentication Proxy’s own debug log. I suggest you enable debug logging on your Duo Authentication Proxy, test the auth from the ASA, and then open the
authproxy.log file on the proxy server to see what output was captured for the incoming request from the ASA and the subsequent response during that authentication test.
If you don’t see any authentication activity in the Duo proxy’s
authproxy.log, then there is likely an issue preventing communications between the Duo proxy and your ASA, and you should examine the network config , firewall, routing, etc.
If there is no
authproxy.log file, then most likely the Duo Authentication Proxy service could not be started. Verify whether the service is started. If it isn’t, try to start it manually. If it will not start and stay running, here are some suggestions.
Keep in mind this forum isn’t a substitute for Duo Support, so if you are still stuck consider contacting them to receive 1:1 troubleshooting assistance.