Troubleshoot a Private Relay connection
Open **Orders → Supplier APIs**, edit the affected relay connection and use **Test Connection**. Keep the installed PHP file, signing key and supplier credentials private while you investigate.
Check the installation
Verify the installed endpoint is a reachable public HTTPS URL. Enter the endpoint itself without a query string or fragment. Confirm the file is configured with the selected supplier driver’s local values and that the server has the required PHP and cURL support.
If the test says the relay is reachable but local supplier configuration needs attention, check the supplier values on your server. Repeatedly downloading the same file does not correct a missing local credential, unsupported supplier authentication flow or wrong supplier account.
Form and driver issues
If secure credentials cannot be generated, open the Admin over HTTPS. If the form asks you to refresh supplier settings before enabling relay, refresh and retry after the required backend support is available. A driver marked unsupported cannot be made compatible merely by turning the switch on.
Some drivers or supplier-specific preset connections do not offer the simple PHP relay. Follow the driver note and supported connection method. Do not put supplier secrets into an unrelated public field to bypass a missing relay control.
Switching back to direct connection
Disabling relay leaves cleared supplier fields blank. Re-enter the direct supplier settings deliberately and save. A relay signing key is not the supplier’s API credential.
**Expected result:** Test Connection succeeds and the saved endpoint remains consistent with the installed file. If support is needed, share the driver, safe error message, approximate time and endpoint host/path without credentials or private query values.