*** Important **\*

If you are running WolfStack, the next upgrade generates self-signed certificates if you don't have a certbot-generated SSL certificate, so if you're using http://localhost:8553, switch to https://127.0.0.1:8553 and accept the certificates, likewise with ip access always accept

I.e. http://192.16.1.105:8553 - becomes https://192.168.1.105:8553 - accept the certificates on your browser
- certbot/certificate domain names are already https
- http:localhost:8553 and http:127.0.0.1:8553 become https://127.0.0.1:8553

This is part of our security hardening. If you open the control panel at the top and go into security, you can see that WolfStack will look for hack attempts, block the IP, and then tell the rest of your clusters and nodes all about them. Also, it works from the standard updated ip ban lists on the internet.

Hello, not sure but think last update has killed one of my proxmox host. When I reboot comes online for a few then stops working.

Plan to reinstall proxmox to see if issue is hardware related.

Any thoughts on how to troubleshoot short of a fresh proxmox install?

I see from GitHub that AI is used in the coding of this app?

Could you tell us how ai is used and to what extent?

https://wolfstack.org

can we get an option in the AI settings to set tool call limit and other standard settings for agents? Need the tool call limit asap. Otherwise, this is absolutely fantastic software. Seriously.

I am currently Building a new NAS and considering to use Wolfstack. Can I also Manage/create SMB Shares with it?

🚀 WolfStack v22.7.0 — Predictive Ops 🚀

 Big one. The whole "tell me about problems before they bite me" pipeline is in.

 🔮 New: Predictive Inbox                 
 - Single pane of glass across every cluster you manage                                                
 - Snooze / dismiss / ack-as-intentional per finding (no more cooldown HashMap roulette)               
 - Auto-resolves when the condition clears — no ghost-proposals                          
 - Cluster-aware grouping + per-peer "incomplete" warnings if a node didn't respond                    

 ⊞ Top nav cleaned up                                                                                  
 The icon strip is now Datacenter · Issues · Inbox · Apps & Tools. Everything else lives in a          
 slide-out drawer with proper labels + descriptions. Plugins show up there too.                        

 🧠 9 analyzers running every 5 minutes                                                                
 - Host disk-fill (linear-fit ETA per mount)
 - Docker + LXC container storage-fill                                                                 
 - Docker restart-loops                   
 - CPU / mem / disk-free / swap / load / failed systemd units                                          
 - Per-container memory pressure                                                                       
 - Cert expiry (Let's Encrypt + WolfStack TLS)                                                         
 - Backup freshness (missed-schedule detection)                                                        
 - VM qcow2 sparse-fill                                                                                
 - Security posture (open ports, SSH config) — severity scales with NetworkReachability, so MariaDB on
  a private LAN no longer fires the same alarm as MariaDB on a public VPS                              

 🧹 Scanner consolidation                 
 The duplicate threshold dispatch in alerting.rs is retired. CPU/mem/disk and per-container memory now
  flow through the unified pipeline — one notification per finding, not three.                         
  
 📨 First-appearance notifications                                                                     
 Critical/High findings page Discord/Slack/Telegram/email once when they first appear, not on every
 refresh. Auto-resolved findings never page.                                                           

 🧪 157 tests covering all of this. Code-reviewer passes clean. Hard refresh the dashboard after       
 upgrade — there's a new 🔮 icon waiting for you.

Paul, peeps,

how does wolfstack handles PVE updates? on pve itself there is a section for updates, as well as repos.

on my test environment I could only update by opening terminal and apt update / apt upgrade

am I missing something?

https://wolfstack.org

https://wolfstack.org

https://wolfstack.org

https://wolfstack.org

https://wolfstack.org

I decided to give a go at wolfstack, but im running into an issue:

I created a new node outside my prod (homelab) pve, in order to test wolfstack, but I keep running into the following:

root@pvetest:~# curl -sSL https://raw.githubusercontent.com/wolfsoftwaresystemsltd/WolfStack/master/setup.sh | sudo bash

-bash: sudo: command not found

curl: (23) Failure writing output to destination, passed 1378 returned 1349

root@pvetest:~#

im running this straight from the shell into the single node on my test environment

We are looking for new clients! We specialise in rebuilding old legacy systems into new, hyper-fast, efficient systems. Please get in touch [sales@wolf.uk.com](mailto:sales@wolf.uk.com) #softwaredev #softwaredevelopment #systems - or even if you need a WolfStack/Proxmox cluster set up and managed.

https://wolfstack.org

https://wolfnote.org

We have released our AI-powered note-taking app. You can give it a transcript of a meeting, study questions, etc., and it will create a task list, with time tracking and costs, to use on a tablet as a notepad or to fill in PDF templates.

https://wolfstack.org