Hi Claas, this sounds strange - is there any error message in the logs when you call the status page? What OS are you using and how do you start OpenXPKI?
Oliver Am 24.01.22 um 11:55 schrieb Claas Hilbrecht: > Hi Oliver, > >> I found this problem yesterday and it will be fixed in the next release >> - the reason is (very likely) that the "ratoken" secret in the >> crypto.yaml has no value which lets the call that fetches the system >> status crash. If this is the case your status screen will look like this >> and *NOT* show any value for system version or hostname. >> >> If this is the case, just remove "secret.ratoken" from crypto.yaml or >> pass a value to it. > > I changed the crypto.yaml below the realm like this: > > File: crypto.yaml > > type: > cmcra: ratoken > token: > ratoken: > inherit: default > key_store: DATAPOOL > key: "[% ALIAS %]" > secret: ratoken > secret: > ratoken: > label: Secret group for RA Token > export: 1 > method: literal > value: test > > But still: > Your system status is critical! > OpenXPKI system status > CRL Status > 2022-02-04 17:45:11 UTC > Active Encryption Token > vault-1 > Watchdog > Not running! > System Version > 3.16.1 > Hostname > openxpki-xxx > Config Version > > api > 3.14 > commit > b69603 > config > 3.14 > > > > > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users > -- Protect your environment - close windows and adopt a penguin! _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
