Genral Questions that I cannot find answers for.

[lslamp]

First and foremost,
Thank you for up to now seems an incredible product. If I can get my issues fixed, I will most definitely contribute financially seeing as I am not good enough to contribute in code.

I feel that these answers are somewhere but for the life of me I cannot find them.

1. what is the username and password to get into the console of the LXC
   Not sure if this will cause issues, but I have my proxmox behind a proxy server, for access to the internet.
2. My installation all went well. My issue is with the VMs. I have added all the details but for some reason they do not appear on the dashboard.
   Could this be because I used the same generated token to add onto 4 VMs. Should I have created a new token for each VM I want to add? I thought it would discover the VMs and add then automatically.

The other question I have, related to searching for a VM.
I have added 4 VMs all called monster01, monster02, monster03, monster04. I have installed the necessary pulse-host-agent and qemu-guest-agent successfully. Both services are running.
when I try searching I only see one VM, why are the others not being found?

Thanks
Lawrence

[rcourtman]

Console access: the installer doesn’t set a password. From the Proxmox host, run pct enter <ctid> to get a shell. If you want the web console or SSH, set a root password once with pct exec <ctid> -- passwd or add your SSH key.

VM visibility: VMs appear after the Proxmox node is added under Settings → Nodes; host-agent tokens don’t register VMs. The PVE installer tries to auto-register the host right after it creates the LXC, but if that was blocked by the proxy or bootstrap timing, run the Nodes setup script manually from the PVE host:
curl -sSL "http://<pulse>:7655/api/setup-script?type=pve&host=https://<pve>:8006&auth_token=<setup-code-or-api-token>" | bash
Once the node is connected, VMs should populate; Guest Agent is only needed for disk metrics.

If the node already shows connected but VMs are still missing, share the Pulse version and what you see in Settings → Nodes.

[lslamp]

I have tried to run the following on a VM that I want to have visible.

curl -sSL "http://192.168.1.6:7655/api/setup-script?type=pve&host=https://192.168.1.5:8006&auth_token=xxxxxxxxxxxebdfe08bc4e3f98138d1f91xxxxxxxxxxxxSXSXSXAS22" | bash

I obtained the auth_token= from settings -> hosts -> generate token.

that gives me the following script which I used to try adding hosts before.

curl -fsSL https://proxmon.lsl-technology.com/install-host-agent.sh | bash -s -- --url https://proxmon.lsl-technology.com --token xxxxxxxxxxxebdfe08bc4e3f98138d1f91xxxxxxxxxxxxSXSXSXAS22 --interval 30s

after trying what you suggested I got the following error.

Pulse Monitoring Setup for Proxmox VE

This script requires Proxmox host tooling (pveum).

Run on your Proxmox host:
curl -sSL "http://192.168.1.6:7655/api/setup-script?type=pve&host=https://192.168.1.5:8006&pulse_url=http://192.168.1.6:7655" | bash

What I then did was go to each VM, then in Settings -> Hosts -> Generate Token. I did this for 10 different VMs, after running the command, the VM appeared as I expected. Luckily I only have about 24 VMs, what would happen if I had 1000. I should not have to go to each machine manually and run the install-host-agent.sh script.

Thanks
Lawrence

[rcourtman]

The node setup script has to run on the Proxmox host because it uses the PVE CLI (pveum) to create the API token and register the node. Running it inside a guest prints “This script requires Proxmox host tooling (pveum)”.

Run this on the Proxmox host (192.168.1.5 in your example) using a setup code from Settings → Nodes or your API token:

curl -sSL "http://192.168.1.6:7655/api/setup-script?type=pve&host=https://192.168.1.5:8006&pulse_url=http://192.168.1.6:7655" | bash

After the node shows Connected under Settings → Nodes, VMs will appear automatically; no install-host-agent.sh on each VM is needed. If the node shows Connected but VMs are still missing, share the Pulse version and what you see on the Nodes page.

[lslamp]

I ran the script as you suggested and it got to the last point and just hung there for multiple hours .... I had to breakout of the command.

below is the extract from the screen.

curl -sSL "http://192.168.1.6:7655/api/setup-script?type=pve&host=https://192.168.1.5:8006&pulse_url=http://192.168.1.6:7655" | bash

Pulse Monitoring Setup for Proxmox VE

Detected Proxmox VE host environment.

What would you like to do?

[1] Install/Configure - Set up Pulse monitoring
[2] Remove All - Uninstall everything Pulse has configured
[3] Cancel - Exit without changes

Your choice [1/2/3]: 1

Proceeding with installation...

Checking for existing Pulse monitoring tokens from this Pulse server...
Creating monitoring user...
User already exists
Generating API token...
API token generated successfully

Setting up permissions...
Setting up additional permissions...
• Applied privileges: Sys.Audit VM.Monitor
Pulse setup token:
⚠️ Auto-registration skipped: no setup token provided

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Temperature Monitoring Setup (Optional)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔧 Refreshing pulse-sensor-proxy installation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Existing proxy detected - updating to refresh tokens and control-plane settings...

✓ pulse-sensor-proxy service is already running
Refreshing configuration and token...

To me that seemed to reinstall everything.

[rcourtman]

Auto registration was skipped because no setup token was provided. Use Settings → Nodes → Add node to copy an installer that already includes auth_token and PULSE_SETUP_TOKEN then run it on the Proxmox host shell not inside a VM. After the host registers the VMs will populate automatically and no per VM tokens are needed.

The pulse sensor proxy refresh should finish within a minute. If it sits longer check journalctl -u pulse-sensor-proxy -n 40 on the host.

Commands to rerun and debug are below

curl -sSL "http://<pulse>:7655/api/setup-script?type=pve&host=https://<pve>:8006&auth_token=...&pulse_url=http://<pulse>:7655" | PULSE_SETUP_TOKEN=... bash
journalctl -u pulse-sensor-proxy -n 40

[lslamp]

I am sorry, I really feel silly, but if I go to Setting -> I do not see Nodes. Going through all the items, I do not see any option to Add a Node.
I do however see Settings -> Hosts -> Generate Token.
then it says that following.
Add a host agent
Generate a token once, then run the matching command on Linux, macOS, or Windows to register new hosts.

Generate API token
Create a fresh token scoped to host-agent:report.
This seems to imply that I need to generate a single token per host.
I do not see any means to generate a single command to run and have the VMs register automatically.

This might be me not understanding but looking under Settings -> Operations -> API Tokens
I do see a full list of VMs that have been registered, but I feel that the list is the VMs that I have ran manually. See below.

[lslamp]

I hope that it is ok to ask some questions here as well.
thinking about what I did. I did the installation according to instructions.
Now looking at the Pules Overview, I have the Node that I created, the PVE is shown, but this is shown with a red dot.

Also something I do not understand is why all the items are showing no data.
Uptime, CPU, Memory, Disk, Temp, VMS, Containers.

If you see below, both the Proxmox server and the Pulse LXC are showing offline, when this is not the fact.

below you can see that I have 3 x LXC devices and 20 VMs. I have only shown you a few VMs.

Below you can see the configuration panel for ProxmoxHome, why are boxed items showing in blue. I assume that they are not configured.

Sorry about the questions but this is all very new and challenging to me. I really like what I see and hope I can get it working.

Thanks
Lawrence

[marcoproenca]

Antes de mais nada, obrigado, pois até agora o produto parece incrível. Se meus problemas forem resolvidos, com certeza contribuirei financeiramente, já que não tenho conhecimento suficiente para contribuir com código.

Sinto que essas respostas estão em algum lugar, mas por mais que procure, não consigo encontrá-las.

1. Qual é o nome de usuário e a senha para acessar o console do LXC?
   Não sei se isso causará problemas, mas meu Proxmox está atrás de um servidor proxy para acesso à internet.
2. A instalação ocorreu sem problemas. Meu problema é com as VMs. Adicionei todos os detalhes, mas por algum motivo elas não aparecem no painel.
   Isso pode ser porque usei o mesmo token gerado para adicionar 4 VMs? Eu deveria ter criado um novo token para cada VM que queria adicionar? Achei que o sistema detectaria as VMs e as adicionaria automaticamente.

A outra dúvida que tenho está relacionada à busca por uma máquina virtual. Adicionei quatro máquinas virtuais, todas chamadas monster01, monster02, monster03 e monster04. Instalei com sucesso os serviços pulse-host-agent e qemu-guest-agent necessários. Ambos os serviços estão em execução. Quando tento pesquisar, vejo apenas uma máquina virtual. Por que as outras não são encontradas?

Obrigado, Lawrence

Bom dia.
Qual é o nome de usuário e a senha para acessar o console do LXC?
No shell do proxmox onde esta a VM do pulse, digite: pct enter
Você caira no shell da VM Pulse (root@pulse:#)
Você pode redefinir a senha do root: passwd root
Se quiser acesso SSH, é preciso alterar a configuração do SSHD_CONFIG
root@pulse:# nano /etc/ssh/sshd_config
PermitRootLogin yes
PasswordAuthentication yes

Você tera acesso a VM Pulse.

Não sei se ajudei muito, ainda estou aprendendo Linux,

[lslamp]

Thanks for the response, I had already found this out and solved my problem.

Lawrence