Troubleshooting

Find quick answers and practical solutions to common deployment and runtime issues, helping you keep your environment running smoothly.

I'm seeing error messages in the SeaweedFS Container

At the start, the SeaweedFS container repeatedly shows two error messages in the log (RPC error and missing pemfile). Both can safely be ignored when using the reference deployment as they are triggered by its internal service being started while polling on each other.

'Unknown User' in transactions

This error originates from the migration to new db structure, which requires exact match of the name and surname in transaction originator and custodial data. Having 'Unknown User' as originator in transactions means that some of the old sent transactions does not match the entry in the customers list.

I'm seeing 'Could not apply database migration' errors in the travel-autod container

Any errors relating to the add_transactions_view migration will be transitory and disappear once the other services have successfully run their migrations. The travel-autod container will automatically restart until this is resolved.

I'm seeing warnings regarding OCSP in the travel-trustd container

If you are seeing warnings that contain OCSP (Online Certificate Status Protocol), it means that the status of the server certificate that you provided for TRUST could not be automatically obtained. This could prevent counterparty VASPs from sending TRUST Travel Rule messages to your VASP. To fix this, ensure that your Certificate Authority provides an OCSP endpoint and that its URL is correctly encoded in the certificate.