Troubleshooting Guide

Cannot connect to APRS-IS

Connection fails or times out when trying to connect to APRS-IS servers.

Solutions:

• Check your internet connection
• Verify the server address is correct (rotate.aprs2.net)
• Ensure port 14580 is not blocked by your network/firewall
• Try a regional server instead of the rotating server
• If on mobile data, check that background data is enabled for the app

Authentication failed

Server rejects your connection with an authentication error.

Solutions:

• Verify your callsign is entered correctly (uppercase)
• Check that your passcode matches your callsign
• The passcode is auto-generated from your callsign - re-enter it if unsure
• If using a club callsign, ensure you have the correct passcode for it

TCP KISS connection refused

Cannot connect to your TNC via TCP KISS.

Solutions:

• Verify your TNC software (e.g., Dire Wolf) is running
• Check the IP address and port number
• Ensure your device is on the same network as the TNC
• Check firewall settings on the TNC host computer
• For Dire Wolf, verify KISSPORT is configured in direwolf.conf

Messages not being received

Connected but not seeing any incoming messages or traffic.

Solutions:

• Check your filter settings - they may be too restrictive
• Try widening your range filter (e.g., r/LAT/LON/200)
• Verify your location is set correctly for range-based filters
• For RF: Check that your TNC is receiving audio from the radio
• For RF: Verify you're on the correct frequency (144.390 MHz in North America)

Messages not being sent

Outgoing messages fail or don't appear to be transmitted.

Solutions:

• Verify you have a valid passcode for APRS-IS transmission
• Check that your callsign is set correctly
• For RF: Verify PTT is triggering on your radio
• For RF: Check TNC TX delay settings (try increasing to 500ms)
• Ensure message content doesn't exceed 67 characters for RF compatibility

No acknowledgment received

Messages send but you never receive ACKs back.

Solutions:

• The destination station may not have ACK enabled
• Check that your filter includes the destination station
• The destination may be out of range or offline
• Some IGates don't gate ACK packets to RF

App crashes on startup

Solutions:

• Clear the app's cache and data
• Reinstall the app
• Ensure your device meets minimum requirements
• Check for app updates in the store

Battery drain

Solutions:

• Reduce position beacon rate
• Use a more restrictive filter to reduce incoming traffic
• Disconnect when not actively using the app
• Disable location tracking when not needed

Connection drops in background

Solutions:

• Disable battery optimization for APRS Chat
• Enable "Keep alive" in connection settings
• On some devices, lock the app in recent apps
• Check manufacturer-specific battery saving settings