I have been using Let's Encrypt for SSL communications with the front-end. I want to switch that to use a certificate issued by our internal CA. Velociraptor is running on Windows Server 2022.
Here's the Frontend section of server.config.yaml
Frontend:
hostname: velo.##########.com
dns_name: velo.##########.com
#use_self_signed_SSL: false
bind_address: 0.0.0.0
bind_port: 443
tls_certificate_filename: C:\data\velo.##########.com.pem
tls_private_key_filename: C:\data\velo.##########.com.key
default_client_monitoring_artifacts:
- Generic.Client.Stats
GRPC_pool_max_size: 100
GRPC_pool_max_wait: 60
resources:
connections_per_second: 100
notifications_per_second: 30
max_upload_size: 10485760
expected_clients: 30000
Datastore:
implementation: FileBaseDataStore
location: d:\########\VR-Data
filestore_directory: d:\########\VR-Data
Logging:
output_directory: d:\########\VR-Data/logs
separate_logs_per_component: true
debug:
disabled: true
info:
rotation_time: 604800
max_age: 31536000
error:
rotation_time: 604800
max_age: 31536000
autocert_cert_cache: d:\########\VR-Data
When I comment out use_self_signed_SSL: false, I get this error:
velociraptor.exe: error: frontend: Unable to load config file: No Frontend.certificate config
When I leave in
use_self_signed_SSL: false, I get a different error:
velociraptor.exe: error: frontend: Unable to load config file: yaml: unmarshal errors:
line 163: field use_self_signed_SSL not found in type proto.FrontendConfig
I'm lost. Any suggestions?