The safedata_server command line API breaks when the metadata server being used doesn't have a proper SSL certificate. It should have one for production us, but during testing and setup it might not. This is definitely an issue when working behind a institutional firewall, where LetsEncrypt is more difficult!
The solution is to have a Resources flag to allow unverified request.post calls.
The safedata_server command line API breaks when the metadata server being used doesn't have a proper SSL certificate. It should have one for production us, but during testing and setup it might not. This is definitely an issue when working behind a institutional firewall, where LetsEncrypt is more difficult!
The solution is to have a Resources flag to allow unverified
request.postcalls.