Learn how to manage Digibee IPs for VPN or internet communication.
Last updated
Was this helpful?
Was this helpful?
Setting up a new VPN or configuring a mapping for an existing VPN with Digibee requires attention to ensure a smooth connection. A common issue during this process is the "Connection refused" error message, which indicates that the server has refused the connection request.
This article explains the key step required after requesting a new mapping in Digibee: allowing Digibee's private IP in the target service's firewall to ensure that traffic can flow correctly.
"Connection refused" is an error message that occurs when a customer tries to connect to a server, but the server rejects the connection request. Common causes are:
Closed ports
Firewall or security settings
Resource restrictions on the server
Incorrectly configured settings
Unavailability of the requested service
After requesting a new mapping in Digibee, make sure that Digibee's private IP is allowed in the target service's firewall settings. If you are unsure of the IP address, contact the Support team to obtain this information.
The Digibee Integration Platform runs on the Google Cloud Platform and uses a dynamic range of IPs for each pipeline execution. If a fixed outgoing IP of the pipeline is required — for example when whitelisting public IPs to access external resources — you can configure a NAT (Network Address Translation) for the host:port that your pipeline needs to access.
To request this configuration and get the public IP for whitelisting, contact our Support team via chat.
