Table of Contents
Blade
Purpose
blade.hackeriet.no is a service VM used by several Hackeriet services.
For inventory details, use the NetBox/IPAM entry blade (VM ID 12). NetBox is the source of truth for VM size, IP assignments, site, tenant, and current placement.
Emergency Access
Normal access:
ssh blade.hackeriet.no
If SSH does not respond:
- Open the NetBox/IPAM entry
blade. - Confirm the current hypervisor from NetBox before assuming placement.
- Current known hypervisor when this page was written:
host007. - Connect to the Proxmox UI/console for the current hypervisor or cluster.
- Cluster name from NetBox:
klynge001.
The VM can move, so always verify placement in NetBox during an incident.
Credentials
Do not paste secrets into the wiki.
Relevant hackeriet/pass entries:
hackeriet@blade.hackeriet.no.gpgmailman@blade.gpg
If root or service credentials are needed, look in hackeriet/pass and keep decrypted values out of the wiki.
Operating System
Observed over SSH on 2026-05-19:
- OS:
Debian GNU/Linux 13 (trixie) - Kernel:
6.12.88+deb13-amd64
Treat this as emergency orientation only. Live state may differ.
Key Services On Blade
Service details belong on the service pages:
Observed service categories:
- nginx-served web services
nsdauthoritative DNS- Hula app service
- mail-related services
- webhook-triggered deployments
Useful Paths
Paths commonly useful during incident response:
/etc/nginx/sites-enabled/etc/nsd/etc/webhook.conf/srv/hackeriet-wiki/srv/webapp-hackerhula/home/blog
Checks During Incidents
Basic host checks:
hostname -f systemctl --failed df -h -x tmpfs -x devtmpfs ip -br addr show scope global
Service checks:
systemctl status nginx nsd systemctl status gunicorn-hula systemctl status webhook journalctl -u nginx -u nsd --since "1 hour ago"
If SSH is unavailable, use the Proxmox console via the current hypervisor shown in NetBox.