Raynet One On-Premises Installation and Operations Guide

This section provides guidance on diagnosing and resolving the most common issues encountered during the the on-premises deployment of Raynet One.

Required File Not Found or Connection Errors

Initialization containers (e.g., keycloak-init) or main services may fail to start if required configuration files, scripts, or database connections are unavailable. Typical error messages include file-not found exceptions in entrypoint scripts or connection timeouts.

Follow these diagnostic and resolution steps in order:

1. Check the container logs

Start by examining the logs of the failing container for detailed error information:

docker logs keycloak-init

2. SSL Errors

SSL/TLS errors often occur when containers access services over HTTPS in environments with corporate PKI or private CAs.

Ensure the root CA certificate (rootCA.crt) is correctly placed in the host directory and properly mounted via docker-compose.yml.

3. Entrypoint or Script Errors

Errors such as

/usr/local/bin/kc-entrypoint: line X:/tmp/kc_realm_init/kc_realm_init: not found

typically indicate:

the script/file is missing inside the container image or a missing volume mount.

Network Issues

All services must communicate via the internal Docker network. Misconfigurations here prevent services from reaching each other.

Validation steps:

Confirm all relevant services are attached to the same network (internal_net).