Skip to main content





Debugger not working

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Symptoms

    • In a debug session, the debugger never reaches a breakpoint.
    • In the middle of a debug session, the debugger just hangs.
    • The debugger stops working.


    During a debug session, Service Studio contacts the environment where the app is deployed. During the session it communicates back and forth several times with the environment. To keep communications fast, Service Studio keeps an open connection to the environment.

    Depending on your anti-virus, firewall, or other network elements you might have in place, it's possible that these elements abruptly close the connection between Service Studio and the environment.

    And that's when the debugger hangs.


    Configure Service Studio so that it establishes a new connection for each request made to the environment.

    In Edit menu, under Preferences, check the Use One Connection per Request in Debugger option.

    By activating this option, it's possible that the debugger feels slower since it's establishing new connections on each request.

    The server stops the debug session


    • In a debug session, Service Studio shows the error: The server has stopped the debug session.
    • Checking the Service Studio error report, it shows the following error message: There was an error while contacting the server: HTTP Forbidden.


    This usually occurs in self-managed environments that have additional network elements (such as load balancers or reverse proxies) that aren't trusted by the OutSystems Platform Server.


    Configure your OutSystems environment to trust the addresses for that inject X-Forwarded-For headers. To do so, follow these steps:

    1. Access Service Center.
    2. Go to Administration > Security > Network Security.
    3. In the Trusted proxy addresses field, add the IP addresses or IP ranges of all network elements.

    More information

    There might be other problems affecting your debug session. Check other reasons for the debugger to misbehave.

    • Was this article helpful?