Bambora API: Troubleshooting 504 Gateway Timeout Errors
Diagnosing and resolving 504 Gateway Timeout errors with Bambora API card terminals. Focus on network port configurations and connectivity issues.
Diagnosing and resolving 504 Gateway Timeout errors with Bambora API card terminals. Focus on network port configurations and connectivity issues.
Consult the official Bambora API documentation for the latest list of required network ports. Typically, port 443 (HTTPS) is essential.
The method for running a ping test varies by terminal model. Consult the Bambora API terminal's user manual for specific instructions. Some terminals may not have this capability.
Low humidity, synthetic clothing, and carpets can increase the risk of ESD. Anti-static mats and regular use of humidifiers can help reduce ESD events.
A 504 error signifies a failure in upstream server communication. Possible causes include incorrect network port configurations, firewall restrictions, DNS resolution failures, or intermittent network connectivity. EMV/NFC transactions require stable, low-latency connections. Signal attenuation due to cable interference or excessive cable length can also contribute to connectivity problems. Electrical Static Discharge (ESD) events near the device during operation can also cause temporary communications errors.
Safe Handling: Unplug the terminal from the power outlet before inspecting or cleaning any cables. Ensure the surrounding area is dry to prevent electrical shock. Avoid touching the metal contacts on the network cables. Do NOT attempt to open the terminal casing, as this will trigger anti-tamper mechanisms and void the warranty.
Regularly inspect network cables for damage and ensure they are properly secured to prevent strain. Clean the terminal's exterior with a dry, anti-static cloth. Position the terminal away from sources of electromagnetic interference (EMI), such as power cables or other electronic devices. Implement surge protection to protect the terminal from power surges and ESD events, particularly during dry winter months.
Many network configuration issues can be quickly diagnosed by temporarily connecting the terminal to a different network (e.g., a mobile hotspot) to see if the 504 error persists. If it does not, the problem likely lies with the original network configuration or firewall.