Skip to content

HermesAgent #1831

Closed
Closed
HermesAgent#1831
Labels
Migration To ProxmoxVE

Description

@MickLesk
MickLesk
opened on May 18, 2026

Name of the Script

HermesAgent

Script Type

CT (LXC Container)

📋 Script Details

#1777

Activity

  1. MickLesk
    added
    task
    Ready For Testing
    and removed
    task
    on May 18, 2026

  2. github-actions commented on May 18, 2026

    @github-actions
    github-actionsBot
    on May 18, 2026 – with GitHub Actions
    Contributor

    The hermesagent script is ready for testing:
    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/hermesagent.sh)"
    Installation sources scripts outside of Community Scripts repo. Please check the source before installing.
    Hermes can execute terminal commands. The agent runs as a dedicated 'hermes' service user for isolation.
    After container startup, login, switch to the hermes user (su - hermes) and run 'hermes setup' to configure your model provider and gateway server.
    OpenAI-compatible API server available at http://:8642/v1. API key is stored in /home/hermes/.hermes/.env.
    Access the web dashboard via SSH tunnel: ssh -fNL 9119:localhost:9119 root@, then open http://localhost:9119

    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

  3. jenishngl commented on May 18, 2026

    @jenishngl
    jenishngl
    on May 18, 2026

    Installed fine for me. But setting up the hermes gateway as a service seems to be a pain

    ⚠   System service install requires sudo, so Hermes can't create it from this user session.
    After setup, run: sudo hermes gateway install --system --run-as-user hermes
    Then start it with: sudo hermes gateway start --system

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✓ Messaging Platforms (Gateway) configuration complete!
hermes@hermesagent:~$ sudo hermes gateway install --system --run-as-user hermes
sudo: hermes: command not found
hermes@hermesagent:~$ exit
logout
root@hermesagent:~# sudo hermes gateway install --system --run-as-user hermes
sudo: hermes: command not found
root@hermesagent:~#

    I fixed it using this command
    created a symlink to the local bin

    sudo ln -s /home/hermes/.local/bin/hermes /usr/local/bin/hermes
sudo hermes gateway install --system --run-as-user hermes
sudo hermes gateway start --system

  4. jomz commented on May 18, 2026

    @jomz
    jomz
    on May 18, 2026

    Installation completed, but when I try to open console, I get a 500 timeout response.
    This should help:

    unexpected extra arguments, use '-h' for usage
    TASK ERROR: command '/usr/bin/termproxy 5901 --path /vms/421 --perm VM.Console --vncticket-endpoint --verify-port --ticket-fd 6 -- /usr/bin/dtach -A /var/run/dtach/vzctlconsole421 -r winch -z lxc-console -n 421 -e -1' failed: exit code 1

  5. MickLesk commented on May 18, 2026

    @MickLesk
    MickLesk
    on May 18, 2026
    MemberAuthor

    You need to Update your Proxmox Host. Its an old known bug

  6. EelmanEmbedded commented on May 20, 2026

    @EelmanEmbedded
    EelmanEmbedded
    on May 20, 2026

    Script hang on "Installing Hermes Agent" on default settings. ProxmoxVED/install/hermesagent-install.sh#L48-L51

        __  __                                 ___                    __
   / / / /__  _________ ___  ___  _____   /   | ____ ____  ____  / /_
  / /_/ / _ \/ ___/ __ `__ \/ _ \/ ___/  / /| |/ __ `/ _ \/ __ \/ __/
 / __  /  __/ /  / / / / / /  __(__  )  / ___ / /_/ /  __/ / / / /_
/_/ /_/\___/_/  /_/ /_/ /_/\___/____/  /_/  |_\__, /\___/_/ /_/\__/
                                             /____/
  ⚙️  Using Default Settings on node ***
  💡  PVE Version 9.1.19 (Kernel: 7.0.2-6-pve)
  🆔  Container ID: 106
  🖥️  Operating System: debian (13)
  📦  Container Type: Unprivileged
  💾  Disk Size: 20 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 4096 MiB
  🚀  Creating a Hermes Agent LXC using the above default settings

  ✔️   Storage local (Free: 11.6GB  Used: 35.0GB) [Template]
  ✔️   Storage local-lvm (Free: 26.5GB  Used: 23.5GB) [Container]
  ✔️   Storage 'local-lvm' (lvmthin) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-13-standard_13.1-2_amd64.tar.zst [local]
  ✔️   LXC Container 106 was successfully created.
  ✔️   Started LXC Container
  ✔️   Network in LXC is reachable (ping)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.***
  ✔️   IPv4 Internet Connected
  ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
  ✔️   Installed Dependencies
  ✔️   Setup Node.js 22
  ✔️   Created Hermes User
  ✔️   Configured Service Environment
  💡   WARNING: This script will run an external installer from a third-party source (https://hermes-agent.nousresearch.com/).
  💡   The following code is NOT maintained or audited by our repository.
  💡   If you have any doubts or concerns, please review the installer code before proceeding:
         🌐   →  https://hermes-agent.nousresearch.com/install.sh

      Do you want to continue? [y/N]: y
  ✖️   Installation failed in container 106 (exit code: 130)

✔ Installation log: /tmp/install-473d4bfd-combined.log

  Error: Aborted by user (SIGINT)

What would you like to do?

  1) Remove container and exit
  2) Keep container for debugging
  3) Retry with verbose mode (full rebuild)

Select option [1-3] (default: 1, auto-remove in 60s): 2

  Container 106 kept for debugging

    Logfile shows Hermes install script was finished. Can't login the created container because I don't know the generated password.

    less /tmp/install-473d4bfd-combined.log
...
  + obsidian
  + openhue
  + pokemon-player
  + minecraft-modpack-server
  + hermes-agent
  + kanban-codex-lane
  + codex
  + claude-code
  + opencode
  + xurl

Done: 89 new, 0 updated, 0 unchanged. 89 total bundled.
ESC[0;32m✓ESC[0m Skills synced to ~/.hermes/skills/
ESC[0;36m→ESC[0m Skipping setup wizard (--skip-setup)

ESC[0;32mESC[1m
┌─────────────────────────────────────────────────────────┐
│              ✓ Installation Complete!                   │
└─────────────────────────────────────────────────────────┘
ESC[0m

ESC[0;36mESC[1m📁 Your files:ESC[0m

   ESC[0;33mConfig:ESC[0m    /home/hermes/.hermes/config.yaml
   ESC[0;33mAPI Keys:ESC[0m  /home/hermes/.hermes/.env
   ESC[0;33mData:ESC[0m      /home/hermes/.hermes/cron/, sessions/, logs/
   ESC[0;33mCode:ESC[0m      /home/hermes/.hermes/hermes-agent

ESC[0;36m─────────────────────────────────────────────────────────ESC[0m

ESC[0;36mESC[1m🚀 Commands:ESC[0m

   ESC[0;32mhermesESC[0m              Start chatting
   ESC[0;32mhermes setupESC[0m        Configure API keys & settings
   ESC[0;32mhermes configESC[0m       View/edit configuration
   ESC[0;32mhermes config editESC[0m  Open config in editor
   ESC[0;32mhermes gateway installESC[0m Install gateway service (messaging + cron)
   ESC[0;32mhermes updateESC[0m       Update to latest version

ESC[0;36m─────────────────────────────────────────────────────────ESC[0m

ESC[0;33m⚡ Reload your shell to use 'hermes' command:ESC[0m

   source ~/.bashrc

[2026-05-20 23:31:05] [ERROR] Interrupted by user (SIGINT)

  7. markycalvert commented on May 21, 2026

    @markycalvert
    markycalvert
    on May 21, 2026
    __  __                                 ___                    __

    / / / /__ _________ ___ ___ _____ / | ____ ____ ____ / /_
    / // / _ / / __ __ \/ _ \/ ___/ / /| |/ __ / _ / __ / __/
    / __ / __/ / / / / / / / ( ) / ___ / /    / / _/ / / / /
    /    / /    /___/    / // // //___// // |_, /___// //_/
    /    ___/
    ✖️ This version of Proxmox VE is not yet supported.
    ✖️ Supported: Proxmox VE version 9.0 – 9.1

  8. mmahmoodictbd commented on May 22, 2026

    @mmahmoodictbd
    mmahmoodictbd
    on May 22, 2026

    Doing the SSH tunnel: ssh -fNL 9119:localhost:9119 root@IP was a pain, I modified the hermes dashboard to able to listen in all interface. Now I can access like http://192.168.2.27:9119/

    sudo systemctl stop hermes-dashboard
    sudo systemctl edit --full hermes-dashboard.service
    ExecStart=/home/hermes/.local/bin/hermes dashboard --host 0.0.0.0 --insecure --port 9119 --no-open
    sudo systemctl start hermes-dashboard

  9. mmahmoodictbd commented on May 22, 2026

    @mmahmoodictbd
    mmahmoodictbd
    on May 22, 2026

    I am getting error for gateway every 5 minutes, now sure why. Investigating.

    .....
2026-05-22 13:16:32,191 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.49 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:21:33,424 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.13 parent_cmdline='/sbin/init'
2026-05-22 13:26:34,675 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.10 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:31:35,922 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.07 parent_cmdline='/sbin/init'
2026-05-22 13:36:37,436 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.09 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:41:38,680 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.06 parent_cmdline='/sbin/init'
2026-05-22 13:46:39,934 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.03 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:51:41,186 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.07 parent_cmdline='/sbin/init'

  10. mmahmoodictbd commented on May 22, 2026

    @mmahmoodictbd
    mmahmoodictbd
    on May 22, 2026

    I am getting error for gateway every 5 minutes, now sure why. Investigating.

    .....
2026-05-22 13:16:32,191 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.49 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:21:33,424 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.13 parent_cmdline='/sbin/init'
2026-05-22 13:26:34,675 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.10 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:31:35,922 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.07 parent_cmdline='/sbin/init'
2026-05-22 13:36:37,436 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.09 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:41:38,680 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.06 parent_cmdline='/sbin/init'
2026-05-22 13:46:39,934 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=113 parent_name=systemd loadavg_1m=0.03 parent_cmdline='/usr/lib/systemd/systemd --user'
2026-05-22 13:51:41,186 WARNING gateway.run: Shutdown context: signal=SIGTERM under_systemd=yes parent_pid=1 parent_name=systemd loadavg_1m=0.07 parent_cmdline='/sbin/init'

    Found the solution:
    systemctl stop hermes-gateway.service
    systemctl edit hermes-gateway.service

    ### Editing /etc/systemd/system/hermes-gateway.service.d/override.conf
### Anything between here and the comment below will become the contents of the drop-in file

[Service]
ExecStart=
ExecStart=/home/hermes/.hermes/hermes-agent/venv/bin/python -m hermes_cli.main gateway run

### Edits below this comment will be discarded
...

    systemctl start hermes-gateway.service

  11. steveonjava commented on May 23, 2026

    @steveonjava
    steveonjava
    on May 23, 2026
    Contributor

    Thanks for the detailed testing, @mmahmoodictbd!

    Installed fine for me. But setting up the hermes gateway as a service seems to be a pain
    and
    I am getting error for gateway every 5 minutes, now sure why. Investigating.

    The intended pattern is install as a hermes user service. For the hermes user enable-linger is already set so the service will launch on system startup. This is better for security and isolation of the hermes gateway process. It also lets the hermes update script stop and start the services without root access. I would recommend removing the system service and installing hermes gateway as a user service. Happy to update the json instructions and add a note on the install output so other users don't fall in this trap.

    Doing the SSH tunnel: ssh -fNL 9119:localhost:9119 root@IP was a pain, I modified the hermes dashboard to able to listen in all interface. Now I can access like http://192.168.2.27:9119/

    This is a big security issue since the hermes gateway is not secured and doesn't even run via https. Anyone can log into your instance and all of your dashboard traffic is exposed to the network. I agree that setting up an ssh tunnel is not a great user experience and I installed a reverse proxy using Caddy on my own instance. However, I think it is better not to overcomplicate the installer right now given the rate of change on the hermes-agent project.

  12. hofmn commented on May 23, 2026

    @hofmn
    hofmn
    on May 23, 2026

    For me everything worked fine. But i did not try to access the Dashboard via ssh.

  13. AfzalivE commented on May 23, 2026

    @AfzalivE
    AfzalivE
    on May 23, 2026

    While running hermes setup, it wants to install other tools (like the tts engine) but it needs a password but the hermes user doesn't have a password set and is not in sudoers.

  14. 2 remaining items

  15. MickLesk commented on May 24, 2026

    @MickLesk
    MickLesk
    on May 24, 2026
    MemberAuthor

    Do you make an PR?

  16. AfzalivE commented on May 24, 2026

    @AfzalivE
    AfzalivE
    on May 24, 2026

    No. I didn't think that would be accepted as default 😅

    Should I?

  17. MickLesk commented on May 24, 2026

    @MickLesk
    MickLesk
    on May 24, 2026
    MemberAuthor

    I mean @steveonjava ^^ He is the responsible for this tool

  18. steveonjava commented on May 24, 2026

    @steveonjava
    steveonjava
    on May 24, 2026
    Contributor

    I filed a PR for the improvement discussed in this thread: #1858

  19. steveonjava commented on May 24, 2026

    @steveonjava
    steveonjava
    on May 24, 2026
    Contributor

    Make that #1859. The automated PR checker was overeager in closing my previous PR for a section marked optional. 🤷

  20. steveonjava commented on May 24, 2026

    @steveonjava
    steveonjava
    on May 24, 2026
    Contributor

    Thanks for helping with the merge, @MickLesk! 🙏

    I noticed one more gotcha. Now that the setup runs as root it creates the gateway service, but is unable to enable/start it automatically. I will file a second PR for this, because it is surprising to new users when they said to start the gateway, but it isn't working.

  21. steveonjava commented on May 24, 2026

    @steveonjava
    steveonjava
    on May 24, 2026
    Contributor

    I added a PR to fix this as well. Once this is merged would appreciate someone running through the full setup flow once more (I did this myself, but always better to have a second person validate):
    #1860

  22. J0ekr commented on May 25, 2026

    @J0ekr
    J0ekr
    on May 25, 2026

    As you asked for feedback on the setup: I just ran the helper script and went through the default installation. I then ran /usr/bin/hermes-setup on root and then switched to the hermes user. Installation went fine. The script does not put .local/bin PATH into the /.bashrc so i still had to do that manually. After fighting for a second with my claude integration from then on it works like a charm.

  23. steveonjava commented on May 26, 2026

    @steveonjava
    steveonjava
    on May 26, 2026
    Contributor

    Thanks for testing, @J0ekr! 🙏 Glad you got it working with Claude.

    On the .local/bin, it should get added to the path by ~/.profile. I just created an instance this afternoon and it is there as expected:

    # set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

    Probably what happened is that you switched to the hermes user with a non-login shell by using:
    su hermes
    The correct pattern is:
    su - hermes

    This will start a login shell and source .profile.

  24. steveonjava commented on May 26, 2026

    @steveonjava
    steveonjava
    on May 26, 2026
    Contributor

    I added a simple PR so when logged in as root you get a reminder on the command to switch to the hermes user:
    #1863

  25. MickLesk
    added
    Migration To ProxmoxVE
    and removed
    Ready For Testing
    on May 27, 2026
  26. github-actions
    locked as resolved and limited conversation to collaborators on May 27, 2026

  27. michelroegl-brunner commented on May 27, 2026

    @michelroegl-brunner
    michelroegl-brunner
    on May 27, 2026
    Member

    Merged with #14751 in ProxmoxVE

  28. michelroegl-brunner
    closed this as completedon May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Migration To ProxmoxVE

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions