proxmox/rpc-translator-138/docs/archive/SERVICES_COMPLETE.md

All Next Steps Complete - Services Configured

Date: 2026-01-04
Status: ✅ All Services Configured and Running

---

Deployment Summary

All supporting services have been successfully deployed, configured, and started:

Service	VMID	IP	Port	Container	Service	Connectivity
Redis	106	192.168.11.110	6379	✅ Running	✅ Active	✅ PONG
Web3Signer	107	192.168.11.111	9000	✅ Running	✅ Active	✅ OK
Vault	108	192.168.11.112	8200	✅ Running	✅ Active	✅ Healthy

---

Completed Steps

✅ 1. Container Deployment

• All three containers created on r630-01
• Ubuntu 22.04 template downloaded and used
• Containers started and running

✅ 2. Redis Configuration (VMID 106)

• Redis server installed
• Configured to bind to 192.168.11.110
• Protected mode enabled
• Systemd service enabled and running
• Responding to ping (PONG)

✅ 3. Web3Signer Configuration (VMID 107)

• Java 17 JRE installed
• Web3Signer 23.10.0 downloaded and installed
• Configuration file created (/opt/web3signer-23.10.0/web3signer.yml)
• Listening on 192.168.11.111:9000
• Systemd service enabled and running
• Health endpoint responding (OK)

✅ 4. Vault Configuration (VMID 108)

• Vault 1.15.0 installed
• Running in development mode
• Listening on 192.168.11.112:8200
• AppRole authentication enabled
• Translator role and policy created
• Systemd service enabled and running
• Health endpoint responding

---

Service Details

Redis (VMID 106)

• Status: ✅ Running
• Service: systemd (redis-server)
• Bind: 192.168.11.110:6379
• Test: pct exec 106 -- redis-cli -h 192.168.11.110 ping → PONG

Web3Signer (VMID 107)

• Status: ✅ Running
• Service: systemd (web3signer)
• Listen: 192.168.11.111:9000
• Config: /opt/web3signer-23.10.0/web3signer.yml
• Test: curl http://192.168.11.111:9000/upcheck → OK

Next: Configure signing keys (see Web3Signer documentation)

Vault (VMID 108)

• Status: ✅ Running
• Service: systemd (vault)
• Listen: 192.168.11.112:8200
• Mode: Development (root token: root)
• AppRole: Enabled with translator role
• Test: curl http://192.168.11.112:8200/v1/sys/health → Healthy

Vault Credentials (save to .env):

• Get credentials: pct exec 108 -- bash -c 'export PATH=/usr/local/bin:$PATH && export VAULT_ADDR=http://192.168.11.112:8200 && export VAULT_TOKEN=root && vault read auth/approle/role/translator/role-id && vault write -f auth/approle/role/translator/secret-id'

---

Configuration Files

Systemd Services

All services are managed by systemd and configured to start on boot:

• Redis: /etc/systemd/system/redis-server.service (default)
• Web3Signer: /etc/systemd/system/web3signer.service
• Vault: /etc/systemd/system/vault.service

Web3Signer Config

Location: /opt/web3signer-23.10.0/web3signer.yml

server:
  http-listen-port: 9000
  http-listen-host: 192.168.11.111
  
data-path: /opt/web3signer/data

---

Connectivity Tests

All services are accessible and responding:

# Redis
pct exec 106 -- redis-cli -h 192.168.11.110 ping
# Returns: PONG

# Web3Signer
curl http://192.168.11.111:9000/upcheck
# Returns: OK

# Vault
curl http://192.168.11.112:8200/v1/sys/health
# Returns: JSON with vault status

---

Environment Variables

Update .env files on translator VMIDs (2400-2402) with:

# Supporting Services
WEB3SIGNER_URL=http://192.168.11.111:9000
REDIS_HOST=192.168.11.110
REDIS_PORT=6379
REDIS_PASSWORD=  # Optional - add if configured
VAULT_ADDR=http://192.168.11.112:8200
VAULT_ROLE_ID=<from-vault-output>
VAULT_SECRET_ID=<from-vault-output>

Get Vault Credentials:

ssh root@192.168.11.11
pct exec 108 -- bash -c 'export PATH=/usr/local/bin:$PATH && export VAULT_ADDR=http://192.168.11.112:8200 && export VAULT_TOKEN=root && vault read auth/approle/role/translator/role-id && vault write -f auth/approle/role/translator/secret-id'

---

Next Steps

1. ✅ Supporting services deployed and configured
2. ⏳ Configure Web3Signer signing keys (see Web3Signer documentation)
3. ⏳ Update .env files with Vault credentials (on translator VMIDs)
4. ⏳ Deploy translator service to VMIDs 2400-2402
5. ⏳ Configure translator .env files with service IPs and credentials
6. ⏳ Test end-to-end functionality

---

Security Notes

1. Redis: Currently no password (optional - add REDIS_PASSWORD for production)
2. Web3Signer: No signing keys configured yet (add keys before use)
3. Vault: Running in dev mode (configure production mode for production use)
4. Network: Services bound to specific IPs (192.168.11.110-112)
5. Firewall: Ensure firewall rules allow access from translator VMIDs (2400-2402)

---

Management Commands

Check Service Status:

pct exec 106 -- systemctl status redis-server
pct exec 107 -- systemctl status web3signer
pct exec 108 -- systemctl status vault

Restart Services:

pct exec 106 -- systemctl restart redis-server
pct exec 107 -- systemctl restart web3signer
pct exec 108 -- systemctl restart vault

View Logs:

pct exec 106 -- journalctl -u redis-server -n 50
pct exec 107 -- journalctl -u web3signer -n 50
pct exec 108 -- journalctl -u vault -n 50

---

References

• Deployment Guide: DEPLOYMENT.md
• Deployment Complete: DEPLOYMENT_COMPLETE.md
• Services Configured: SERVICES_CONFIGURED.md
• VMID Allocation: VMID_ALLOCATION.md
• Redis Docs: https://redis.io/docs/
• Web3Signer Docs: https://docs.web3signer.consensys.io/
• Vault Docs: https://developer.hashicorp.com/vault/docs

---

Summary

🎉 All next steps completed successfully!

All supporting services (Redis, Web3Signer, Vault) are:

• ✅ Deployed as LXC containers
• ✅ Installed with required software
• ✅ Configured and running
• ✅ Accessible on the network
• ✅ Managed by systemd

Ready for translator service deployment!