| Issue | Probable Cause | Resolution | |-------|----------------|-------------| | "Connection refused" | Wrong port or server not yet live for your region | Confirm new host/port via official Digicon notification | | "Certificate unknown" | Self-signed cert on new server | Compare SHA256 fingerprint with provided one; then trust temporarily or permanently | | "Authentication failed" | Using old credentials or case-sensitive error | Request new credentials; ensure username is exact | | "Timeout after 20 seconds" | Firewall blocking passive mode ports | Configure client to use passive mode; ask Digicon for port range (e.g., 50000-50100) | | "Directory listing failed" | Old FTP vs. new FTPS mismatch | Switch protocol to FTPS or SFTP |
A junior NOC engineer, Maya , needed to push a critical antenna tilt config update to 50 remote sites before sunrise. The old FTP script failed because it didn’t support TLS. She found a hidden README on the internal wiki: digicon telecommunication ltd ftp server new
: Most private FTP servers from telecommunication firms require an internal IP address (being on their network) or specific login credentials provided to clients. | Issue | Probable Cause | Resolution |
Their infrastructure is built with double-layered backup generators and intelligent system architecture to ensure 24/7 data availability even during power failures. She found a hidden README on the internal
There was only one file: OUTAGE_LOG_FINAL.txt .