Frontend not listening on port I specify?

4 views
Skip to first unread message

Michael Butler

unread,
Jan 12, 2026, 5:56:44 PM (3 days ago) Jan 12
to velociraptor-discuss
Hi folks, I configured my server YAML to bind Frontend to port 8009 and use plain HTTP (because I want to do SSL termination on the AWS Load Balancer). This is on an Ubuntu Linux 24.04 server. When I restart the service using systemctl, and I check my system with ss or netstat, I do not see this port listening by Velociraptor. I do see 8001, 8003, and 8004 as well as 80 & 443 but never the custom port I specify for Frontend. Here's my config snippet:

```
Frontend:
  hostname: velo-frontend.MYDOMAIN.com
  bind_address: 0.0.0.0
  bind_port: 8009
  use_plain_http: true
  certificate: |
    -----BEGIN CERTIFICATE-----
   (removed)
```

GUI seems to be working fine when I configure HTTP only and a custom port.

Does Velociraptor really support running a custom port for the Frontend? 

Thank you,
Michael B

Mike Cohen

unread,
Jan 12, 2026, 6:01:22 PM (3 days ago) Jan 12
to Michael Butler, velociraptor-discuss
Can you please go through the troubleshooting steps? 


In partially look for messages around the starting of the GUI and frontend ports

If I had to guess I would say you are still using auto cert which is forcing both GUI and frontend on port 443. Make sure you have that disabled. 

Thanks
Mike


Mike Cohen 
Digital Paleontologist, 
Velocidex Enterprises
mi...@velocidex.com 

--
You received this message because you are subscribed to the Google Groups "velociraptor-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to velociraptor-dis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/velociraptor-discuss/68bd1697-2109-4cd5-8cff-92bd8598330en%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages