Issues with Rublon Authentication Proxy may have many sources, but mostly come down to one of several cases.
Test Rublon Authentication Proxy Connection
First of all, try to locate the source of your issue. A simple ping & debug tool like NTRadPing allows you to test any RADIUS server, including Rublon Authentication Proxy. Use NTRadPing to send a request to your proxy server. If you get a successful response, then the Rublon Authentication Proxy configuration works correctly, which means that your issue probably stems from your service’s (e.g., VPN’s) configuration.
Some services offer their own debug tools. For example, pfSense allows you to test your Authentication Server (Rublon Authentication Proxy) connection.
Review Your Configuration File
If your NTRadPing test did not succeed, review your Rublon Authentication Proxy configuration file located in rublonauthproxy/config.
Check File Structure
Ensure your file uses a proper JSON convention. All property names must be uppercase. Double-check that your file contains no spelling mistakes.
Recheck Your Tokens
Ensure application tokens set in your configuration file are correct.
Copy values of RUBLON_TOKEN and RUBLON_SECRET from your Authentication Proxy application in the Rublon Admin Console and paste these values into your Rublon Authentication Proxy configuration file.
Note: You must copy the Authentication Proxy application tokens, not the organization tokens.
Recheck Your RADIUS Secret
RADIUS_SECRET is one of the properties you set in your Rublon Authentication Proxy configuration file. You must generate RADIUS_SECRET yourself. Most services you integrate with Rublon require this value. For example, during OpenVPN on pfSense configuration, you must enter the value of RADIUS_SECRET in the Shared Secret field under RADIUS Server Settings.
Review Your Integration Configuration
The mistake may be on the integration’s side.
Use Rublon Authentication Proxy as a RADIUS Server
Remember that Rublon Authentication Proxy acts as a RADIUS server, so when you configure your integration, always act as if you were configuring RADIUS. For example, while configuring Rublon for OpenVPN on pfSense, you must set Type to RADIUS (in Authentication Servers) even if you use Active Directory or OpenLDAP as your identity provider. If you set Type to LDAP, your configuration will not work.
Examine Your Firewall
Rublon Authentication Proxy uses UDP ports 1812 and 1813 for communication. Your firewall might be blocking Rublon Authentication Proxy from communicating with Rublon API. Temporarily turn off your firewall and check if this fixes your issue. If Rublon Authentication Proxy works when your firewall is off, then you must add Rublon to the allowlist in your firewall.
Check Your Network Settings
If all other advice proved fruitless, your issue is probably connected to your network.
Rublon Authentication Proxy and your integrated service (e.g., VPN) must be in the same subnet so that they can ping each other. Otherwise, communication is not possible. You may be able to circumvent this requirement by a custom configuration on your network.
Issue Still Persists
If you still have issues or questions, contact Rublon Support.
You can send us your configuration file, and we will review it for you.