Arjan H.

The output of your netstat command shows what is running on the **host machine**, the conflict is inside the **docker container**. The command `docker exec labca-boulder-1 ps -ef` shows all...

This is only the client side error, it does not contain any information on why the server returns the status 500. Please have a look at the log files, also...

Well, first of all, if your hostname is acme-certmanager.nd.dakota.home, then the domain name is "nd.dakota.home" and not just "dakota.home". Yes, LabCA should work with either of those domains. The system...

You did correct in including all three values (the root and both sub domains) in the whitelist! If you only added the root domain you would probably hit the ratelimit...

The value **does** matter, it should be the value of the "issuerDomain" from file /home/labca/boulder_labca/config/va.json (or `docker compose exec boulder cat labca/config/va.json` if you used the docker-only setup). So that...

You'll need to trust the LabCA root certificate first on the opnsense instance. Opnsense tries to communicate with https://acme-certmanager0.dakota.home but the certificate of LabCA is not trusted until you explicitly...

To know if the installation of the server was successful: go to https://myLabCAserver.home/admin/ with your browser, and after you have completed the setup, LabCA will have successfully requested a certificate...

I'm sorry but you can actually skip that step now and just do `docker compose up -d`. I have updated the README to remove that step

> control-1 | Response: {'type': 'urn:ietf:params:acme:error:serverInternal', 'detail': 'Error finalizing order', 'status': 500} This is only the client side error, it does not contain any information on **why** the server returns...

Thanks, that will help me in analysing this issue and hopefully solving it