fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
95 lines
2.1 KiB
Markdown
95 lines
2.1 KiB
Markdown
# ✅ Proxmox Credentials Configured
|
|
|
|
**Last Updated:** 2026-01-31
|
|
**Document Version:** 1.0
|
|
**Status:** Active Documentation
|
|
|
|
---
|
|
|
|
Your Proxmox connection has been configured with the following details:
|
|
|
|
## Connection Details
|
|
|
|
- **Host**: ml110.sankofa.nexus (192.168.11.10)
|
|
- **User**: root@pam
|
|
- **API Token Name**: mcp-server
|
|
- **Port**: 8006 (default)
|
|
|
|
## Configuration Status
|
|
|
|
✅ **.env file configured** at `/home/intlc/.env`
|
|
|
|
The API token has been created and configured. Your MCP server is ready to connect to your Proxmox instance.
|
|
|
|
## Next Steps
|
|
|
|
### 1. Test the Connection
|
|
|
|
```bash
|
|
# Test basic MCP server operations
|
|
pnpm test:basic
|
|
```
|
|
|
|
### 2. Start the MCP Server
|
|
|
|
```bash
|
|
# Start in production mode
|
|
pnpm mcp:start
|
|
|
|
# Or start in development/watch mode
|
|
pnpm mcp:dev
|
|
```
|
|
|
|
### 3. Verify Connection
|
|
|
|
The MCP server should now be able to:
|
|
- List Proxmox nodes
|
|
- List VMs and containers
|
|
- Check storage status
|
|
- Perform other Proxmox operations (based on token permissions)
|
|
|
|
## Security Notes
|
|
|
|
- ✅ **PROXMOX_ALLOW_ELEVATED=false** - Safe mode enabled (read-only operations)
|
|
- ⚠️ If you need advanced features (create/delete/modify VMs), set `PROXMOX_ALLOW_ELEVATED=true` in `.env`
|
|
- ⚠️ The API token secret is stored in `~/.env` - ensure file permissions are secure
|
|
|
|
## Troubleshooting
|
|
|
|
If you encounter connection issues:
|
|
|
|
1. **Verify Proxmox is accessible**:
|
|
```bash
|
|
curl -k https://192.168.11.10:8006/api2/json/version
|
|
```
|
|
|
|
2. **Check token permissions** in Proxmox UI:
|
|
- Go to: https://192.168.11.10:8006
|
|
- Datacenter → Permissions → API Tokens
|
|
- Verify `root@pam!mcp-server` exists
|
|
|
|
3. **Test authentication**:
|
|
```bash
|
|
# Test with the token
|
|
curl -k -H "Authorization: PVEAPIToken=root@pam!mcp-server=<token-secret>" \
|
|
https://192.168.11.10:8006/api2/json/access/ticket
|
|
```
|
|
|
|
## Configuration File Location
|
|
|
|
The `.env` file is located at:
|
|
```
|
|
/home/intlc/.env
|
|
```
|
|
|
|
To view (token value will be hidden):
|
|
```bash
|
|
cat ~/.env | grep -v "TOKEN_VALUE=" && echo "PROXMOX_TOKEN_VALUE=***configured***"
|
|
```
|
|
|
|
---
|
|
|
|
**Configuration Date**: $(date)
|
|
**Status**: ✅ Ready to use
|
|
|