Monitoring Your Self-Hosted AI Server
A few minutes checking your Ollama and nginx logs each week can catch a problem, like unexpected access attempts, before it becomes a real one. This walkthrough shows the actual commands to check.
Reading is great. Tracking makes it stick. Sign up for a free Dashboard to tick off tasks and see your Security Score.
Get my free Dashboard →
Cyber Nova AI helps you prepare for Cyber Essentials. It doesn't award or certify it. Follow the steps here to get ready, then apply for certification through an accredited Cyber Essentials body when you're set.
What you will need
- Ollama installed and running as a systemd service (Linux)
- The nginx login screen set up, if you followed that guide
- About 10 minutes
Check Ollama’s own logs
View recent activity and any errors Ollama has logged:
journalctl -u ollama --since "1 hour ago"Note: Change the time period to suit, for example "1 day ago" for a longer check.
Watch logs live while testing
Follow new log entries as they happen, useful while you are actively testing a change:
journalctl -u ollama -fNote: Press Ctrl+C to stop following.
Check nginx access logs, if you added a login screen
See who has been accessing Ollama through nginx, and from where:
sudo tail -n 100 /var/log/nginx/access.logNote: Look for repeated failed login attempts or requests from IP addresses you do not recognise.
Decide what is worth acting on
A single failed login is usually nothing. Many failed attempts in a short time, or requests when you know nobody should be accessing the server, are worth investigating.
What you will have at the end
A regular habit of checking what is actually happening on your self-hosted AI server, rather than assuming it is fine because nothing has gone wrong yet.
Why this is worth a few minutes a week
Most home AI setups run quietly with nobody checking on them. A brief regular look at the logs is the difference between noticing a problem early and finding out about it much later, the same principle as checking your router’s connected devices list.
Frequently asked questions
How often should I check these logs?
A quick check every week or two is reasonable for most home setups, more often if you have deliberately exposed the server for remote access.
What counts as suspicious in the logs?
Repeated failed login attempts, requests from unfamiliar IP addresses, or activity at times you know nobody in your household would be using it.
Do I need special monitoring software?
Not for a typical home setup. The built-in logging covered in this guide is enough for most people; dedicated monitoring tools are more useful for larger, more exposed setups.
Track your AI safety progress. Free.
Create a free account to tick off tasks, see your Security Score improve, and know exactly what you've done and what's still to do.
Start your free security check