No problem at all! I was reluctant to comment as it seemed that you weren’t interested in pursuing Nextcloud any further, but went ahead with my comment because I initially had very poor performance when using the basic container running with SQLITE.
I will admit that I had sync issues with a notes program when putting the file on Nextcloud. Some apps just aren’t compatible with that storage paradigm it would seem.
Thanks for the thoughtful replies and good luck on your search!
Let’s dig into performance a bit. Your gen8 server i believe is using E5-26xx CPUs which is plenty of power for speedy performance in Nextcloud. You mentioned upgrading the CPUs and RAM so should be good to go.
volumes: - /HDD_storage/nextcloud/data:/var/www/html
With all of that working correctly, Nextcloud is very performant on my comparable Dell R720.
Edit, I see below you are on a microserver. I think all of the above still applies but I don’t have any experience with that hardware. I would still expect it possible to perform well on that device.
The article is misleading by leaving out critical details about the amount of energy actually used in the test.
That said, progress is progress.
Per Caddy documentation, port 80 is also required, and now I suspect the not serving that port is causing Caddy to fail to issue you a tls certificate.
Try adding a simple text response like this (warning, formatting may not be perfect due to typing on mobile). Also setup a port forward on your router to your caddy host on port 80.
my-domain.com:80 { respond “Buzz off” }
Hopefully this will kick off the tls registration and then get your site on 443 working as well.
Proxmox PVE gang. Excellent platform to self-host anything you could want to run from Windows/Linux VMs, LXC containers, Docker, or mix and match. The web GUI makes management easy and gives you a nice dashboard too.
Document everything. Found a useful link that helped you configure something? Copy the link. Finally got your proxy working right? Save the config. Even just make notes of how you set things up.
Refine and build you notes along with your knowledge.
Eventually, consider keeping all your config files in a self-hosted repository like Gitea.
Oh, and when stuff breaks it’s probably DNS.
A few things may be going on.
The errors seem focused on the tls certificate, which caddy tries to automatically provision.
First, in your caddyfile, “my.server” should reflect the real address used for access. Something like “jellyfin.my-domain.com”. This is important for the tls certificate to be generated correctly.
Once updated, pull out a cell phone, turn off wifi (use LTE/5G), and verify it can connect to your site. This makes sure you can access from outside your home network.
Once confirmed working, try again from your home network. Most likely the page will timeout. This will be due to DNS pointing you back to your own network, which can cause trouble. This can be solved several ways. One is by adding a static DNS entry which points to the IP of your caddy server. You can do this on a per system basis in the hosts file, or at the lan level with you DNS server or router, assuming it allows you to add a custom DNS entry. I do this with my Mikrotik router.
That should get things working internal and external.
The memes on Lemmy have been delightful in that many of them legitimately make me laugh. Keep up the good work!
Worse plug how? You can buy DP cables without the locking mechanism.
Example