Proxmox Container Log File Location: Host Console Log vs. Inside the Container

Proxmox container log file location trips people up because there are two different logs: the host-side console log and the container’s own syslog. The host log is at /var/log/pve/lxc/<CTID>.log on the Proxmox node. The container’s internal logs are inside the container at /var/log/syslog.

Host-level console log

Every LXC container gets a console log on the Proxmox host. It captures boot messages, service startup, and anything written to the console. The path is straightforward:

/var/log/pve/lxc/100.log

Replace 100 with your container ID. You can tail it live while the container boots or crashes:

tail -f /var/log/pve/lxc/100.log

This log is managed by Proxmox and survives container restarts. It’s the first place to check when a container won’t start or dies unexpectedly. If the container is stopped, the log still shows the last boot attempt.

Inside the container

If the container is running and you need application-level logs, you have to go inside the container itself. The standard syslog location applies:

pct enter 100
cat /var/log/syslog

Or if you have SSH set up inside the container, just SSH in and look at /var/log/syslog. That’s where most services write their logs unless they’re configured otherwise. Some containers use journald, so journalctl might be more useful.

Why the confusion?

People often look for container logs on the host and find nothing but the console log. They assume that’s all there is. Then they wonder why their web server errors aren’t there. The host console log doesn’t capture application output—it’s just the console. For real troubleshooting, you need both.

If you’re dealing with a crashing container, check the host log first to see if it even boots. Then go inside for the application logs. That order saves time.

For more on diagnosing container issues, see VPS Crashing on Proxmox: Diagnose It with qemu-server and LXC Logs.