Celigo · On-premise agent
On-premise agent: Unable to bind to 0.0.0.0:7017
Short answer
This Celigo on-premise agent log error is expected a few times before the agent connects to the tunnel, and matters only when it recurs continuously. If the error recurs often and continuously, contact Celigo Support.
VerifiedLast verified
01Error text
level=error, logName=forwardInError, code=undefined, message=Unable to bind to 0.0.0.0:701702Likely causes
- Temporary network instability or server load fluctuations.
- Stale connections that are not cleared quickly, so the agent tries a stale port.
03How to fix it
- If the error recurs often and continuously, contact Celigo Support.
iNotes
The error is expected about three times before the agent connects to the tunnel. If it recurs continuously, the agent may appear Offline (red).
04Official documentation
→Related errors
- On-premise agent: Offline (red) statusAn Offline (red) status for a Celigo on-premise agent means the agent is not running, its token does not match, or a firewall or proxy is blocking it. Check that the agent is running, that its token matches the token in integrator.io, and that no firewall or proxy blocks it.
- On-premise agent: No logs or empty log filesMissing or empty log files for a Celigo on-premise agent mean the agent is running with incorrect permissions, or the log path is misconfigured or inaccessible. Determine whether the log files exist on the machine.
- On-premise agent: Failed to uninstall old application filesThis Celigo on-premise agent error means the Windows system PATH environment variable is corrupted or inconsistent after the agent auto-update. Restart the system.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Celigo work:Open Celigo jobsCeligo rates and salaries