First CT & access issues


New Member
Oct 27, 2023
I just realized in Proxmox I have option to use containers instead of some VMs. My idea is to move mopidy & snapserver from VM to CT. I created new one from template (22.04). Then I done update, dist-upgrade, installed screen, vim, mopidy, snapserver, pip3, Mopidy-Iris, Mopidy-Tidal. My mopidy VM is based also on ubuntu, so I copied all configuration:
I tried restarting mopidy & snapserver services and even whole container. I can log in over ssh, but container has nothing on default 6680 port. There should be at least a simple web page. Probably this is not a question about Proxmox, but some configuration, but I have no knowledge. Can you help me? What should I check? What to look at? I'm already repeating all steps on new VM to check if I can manage my idea to work no slightly different system. I'll update this thread when I have any new observations.
To debug issues with your services, you can typically look at the system journal output with journcalctl -b0 and look at the status of your systemd services with systemctl status <service>.
Assuming that the services you try to run are started via systemd.
OK, I repeated the steps and I have no idea what was wrong... I only changed host in mopidy config from local DNS name to IP and it helped. Unfortunatelly that was another CT, because not working one was on USB HDD which fs (ZFS) died after power loss.


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!