---
title: Troubleshooting a RADIUS gateway instance
description: If the gateway instance isn't healthy, use the information in this section to troubleshoot any issues.
component: pingone
page_id: pingone:integrations:p1_troubleshooting_a_radius_gateway_instance
canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_troubleshooting_a_radius_gateway_instance.html
revdate: February 24, 2026
section_ids:
  i-want-to-view-the-audit-logs: I want to view the audit logs
  my-connection-is-taking-too-long-to-resolve: My connection is taking too long to resolve
  i-want-to-increase-scalability: I want to increase scalability
---

# Troubleshooting a RADIUS gateway instance

If the gateway instance isn't healthy, use the information in this section to troubleshoot any issues.

The following information applies to the various gateway deployment scenarios. You can use the gateway details page, gateway logs, or Splunk reports to identify issues. Learn more in [Verifying a gateway instance](p1_verifying_gateway_instance_radius.html) and [Monitoring activity with Splunk](../developer_tools/p1_monitor_activity_splunk.html).

## I want to view the audit logs

You can view logs to get detailed information about the Gateway service. The method to do so varies depending on your gateway configuration.

* Gateway as a standalone service

  By default, the gateway saves log files to the `./logs` directory on the computer running the gateway. Log files roll over by date.

  To view the logs, go to the `./logs` directory. The logs are named `GatewayStandalone.yyyymmdd.log`

* Gateway as a Windows service

  By default, the gateway saves log files to the `./logs` directory on the computer running the gateway. Log files roll over by date.

  To view the logs, go to the `./logs` directory. The logs are named:

  * `GatewayService.yyyymmdd.log`

  * `GatewayWrapper.yyyymmdd.log`

    |   |                                                                                                                    |
    | - | ------------------------------------------------------------------------------------------------------------------ |
    |   | The `GatewayWrapper.yyyymmdd.log` file mirrors the console output of the standalone version, with additional logs. |

* Gateway as a Docker container

  To view logs for a Docker container, run the following command:

  ```
  docker logs  _<container ID or name>_
  ```

## My connection is taking too long to resolve

If your connection is taking a long time, check the following:

* If the connection is configured with a string host name, try using an IP address instead.

* On the server that you want to connect to, ensure that the desired port is open.

* Ensure there aren't any routing issues in your infrastructure that could affect the ability of the gateway server to reach the LDAP server or Remote Authentication Dial-In User Service (RADIUS) *(tooltip: \<div class="paragraph">
  \<p>A client/server networking protocol providing centralized user management.\</p>
  \</div>)* client.

* Sometimes it can take several seconds for the connection information to be updated in the console user interface. Try refreshing the page to get the most current information.

## I want to increase scalability

For high-availability applications or scalability, you can deploy multiple gateways. You can then run the Windows service, Docker container, or Java application on multiple servers.

When multiple gateways are deployed, load balancing is handled by your RADIUS client's load balancing mechanism, not by PingOne. Your client is responsible for distributing authentication requests among the available gateway instances and for detecting and bypassing any unavailable instances.