Setup problems with Duo Access Gateway for Windows



I got some problems with the initial setup of DAG.
The logging is not giving me anything to go on, at least I cant see it.

I have installed a fresh windows server 2016 standard. Followed the DUO guide to install DAG.
No errors or anything, so far so good.

But now when I launch my browser to continue I only get prompted with the error “Bad request received”.


Entry in my dag.log is the following:

May 02 08:27:29 simplesamlphp ERROR [b05873c03c] SimpleSAML_Error_BadRequest: BADREQUEST_HIDE_REASON(’%REASON%’ => ‘The Duo Access Gateway Launcher is not configured. Please create a Duo Access Gateway application in the Duo Admin Panel and configure it in the Launcher settings page of the Access Gateway Admin Console.’)|Backtrace:|0 C:\inetpub\wwwroot\dag\www\launcher.php:18 (N/A)
May 02 08:27:29 simplesamlphp ERROR [b05873c03c] Error report with id 6fdf72b5 generated.

Cant get past this, any help is welcomed! :slight_smile:

Edit: Yes I have search the forums but did not find anything related to this.

Thank you!

//Best Regards


Hi Patrik,

Please ensure you’re going to, not just to reach the DAG Admin Console.

There is also the following shortcut available in Windows: Start Menu > Duo Access Gateway > Configure


Hi Dooley,

Ah yes now you reminded me about one thing that seems a bit confusing, lets see if I can explain this :slight_smile:

When I browse for I get the above error page
When I browse for I get a 404

The url redirects me to

So actually the …/launcher.php gives me the error, and that might not be so strange. But then the questions is, how come I get a 404 on the main page.

//Best Regards


Ah, It is solved now.

Had my mind set on the first error.

The issue was in our network and that the DAG-server was reporting that is tried to access the webpage from an other ip (or gateway acctually).

Resolved it and now I can access the “set password” page.

Thanks! :slight_smile:


Hi Patrik,

I chatted with some members of our Support Team about this, and they suggested the two following possible solutions:

  1. This could be related to your browser’s security settings. Please try accessing from a freshly updated version of Chrome or Firefox to see if it resolves your issue.
  2. If you’re running the DAG on an externally-hosted VM, please reference this knowledge base article: to resolve your 404 issue.