Language: Deutsch · English
Installation FAQ
Common questions about installation, production use, updates and HTTPS.
HOW-TO OPERATIONS UPDATED: JUL 2026 APPLIES TO NUCLOS 4.2026.X
On this page
Nuclos won't start
If the installation succeeded but Nuclos won't start, server.log in <NUCLOS-HOME>/logs reveals the cause. You can post the log in the Nuclos forum.
Checklist before going to production
Production
Server & client
- 64-bit OS and current Java (11 recommended).
- Secure the client↔server connection via HTTPS (TLS).
- Fast network between server and database (ideally same host, or 1/10 GBit).
Backups
- Regular automatic DB backups plus system backups of DB and Nuclos hosts.
- Keep backups in a separate location and test restores regularly.
- Back up the Nuclos base directory (incl.
/data).
Maturity
- Configuration tested; Nuclos ran for several weeks in parallel/test operation without issues.
Updating to a newer Nuclos version
Updates are largely automatic. Still:
- Read the release notes – they may list required manual steps.
- Do a test update first on a test server using a backup of production.
- Create an additional DB and system backup before the production update.
Configure HTTPS / TLS
HTTPS needs an X.509 certificate stored in a keystore, specified during installation. Obtain it from a CA or create one with the Java tool keytool:
keytool -genkeypair -keystore .keystore -storepass changeit
Test/intranet only
A self-signed certificate is no substitute for a CA certificate and triggers security warnings. In production always use a CA certificate and run Nuclos over HTTPS only.
JCE no longer required
With modern Java (8u161+, 11, 17) Unlimited Strength is enabled by default – the old JCE policy files are no longer needed.
Server locale (Linux)
For correct date/number formats the server should run with the appropriate locale. Check with:
locale
Adjust it per your OS documentation if needed.
Related pages
Überblick
Inhalte