405 connection error when using debugger (4.4.0.)

Hi, We are testing our upgrade to 440 and tried to connect the debugger to a running server based deployment (not hosted in the cloud). I enter the application URL and the MxAdmin password and encounter the following error: System.Net.WebException: The remote server returned an error: (405) Method Not Allowed. at System.Net.HttpWebRequest.GetResponse() at Mendix.Modeler.MicroFlows.Debugger.DebuggerClient.DoHttpRequest(String url, String password, String userAgent, String json, Int32 timeout) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Modeler\MicroFlows\Debugger\DebuggerClient.cs:line 197 at Mendix.Modeler.MicroFlows.Debugger.DebuggerClient.PerformRequest(DebuggerRequest request, Int32 timeout) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Modeler\MicroFlows\Debugger\DebuggerClient.cs:line 164 at Mendix.Modeler.MicroFlows.Debugger.DebuggerClient.StartSession(IEnumerable1 breakpoints) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Modeler\MicroFlows\Debugger\DebuggerClient.cs:line 64 at Mendix.Modeler.MicroFlows.Debugger.DebuggerControl.<>c__DisplayClass2a.<StartDebugging>b__28(DebuggerClient c) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Modeler\MicroFlows\Debugger\DebuggerControl.cs:line 253 at Mendix.Modeler.MicroFlows.Debugger.DebuggerControl.<>c__DisplayClass101.<>cDisplayClass12.<clientdosync>bf() in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Modeler\MicroFlows\Debugger\DebuggerControl.cs:line 101 at Mendix.Modeler.Utility.Progress.ProgressUtil.<>cDisplayClass4`1.<do>b3(ProgressInfo info) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Mendix.Modeler.Utility.Gui\Progress\ProgressUtil.cs:line 25 at Mendix.Modeler.Utility.Progress.Step.Run(ProgressInfo info) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Mendix.Modeler.Utility.Gui\Progress\Step.cs:line 22 at Mendix.Modeler.Utility.Progress.Process.worker_DoWork(Object sender, DoWorkEventArgs e) in c:\cygwin\home\autobuild\build\Mendix-4\modeler\Mendix.Modeler.Utility.Gui\Progress\Process.cs:line 91 at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) Any recommendations? Kind regards, Brian
2 answers

440 release by default only allows access to the runtime server port for localhost. This was blocking our connection. We have set it to public and are now able to connect on port 8080.

After enabling the debugger in the Service console and obtaining the password to login we could debug successfully.

1 remark and 2 remaining question:

  • Remark: there is no/hardly any documentation on the windows based service console (e.g. in the debug description on the mendix website only the cloud webforms are displayed). It would be convenient to also have the documentation include the Windows Service Console.

  • Question 1: The debugger has a timeout. After enabling it, after sometime it is automatically disabled (at least it seems like it does). When re-enabling teh debugger we need to obtain the newly generated password and use that to connect. What is the timeout period? And is it correct that I need to use a new password everytime I use debug?

  • Question 2: We do not want to keep the runtime server port set to Public. There is a field Custom that allows for an alternative entry. What is the syntax that can be used to specify IP addresses (e.g. we want localhost and 1 or 2 IP addresses).

Answers to these questions might be relevant to be added to the documentation.

Kind regards,


Hint: Using a breakpoint condition like: $currentUser/Name = 'x.xxxxx' Enables you to debug the application for 1 specific user only instead of bothering all users.


2 questions... are you going to your application url/debugger/ as mentioned in https://world.mendix.com/display/howto40/Debugging ?

And is the debugger actually enabled? I believe you need the latest service console for this if you are running on premise.

The MxAdmin password definitely won't work for debugging btw, it's a separate password that you set using the service console.