Would love to hear the highlights of what PenguinCoder did to remediate things.
dleewee
joined 2 years ago
The problem is the crazies started getting voted into office. Not a ton, but enough now to start driving the party narrative. They don't listen to reason, they don't compromise, and they have no grip on reality. They would rather burn it all to the ground than let one more gay person get married, one more woman make her own health care choice, or etc. Their own party doesn't even know wtf to do about it.
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!
What about orange juice on cereal? I was skeptical, but a bit of web searching turns up some small percentage of the population actually chooses that life.
It's been ages since I ran into a site issue, using both desktop and mobile Firefox. Not saying it doesn't happen, but seems that issues are very few and far between these days.
I have done this before by setting up a Wireguard VPN link between my home server and a VPS, and then running a reverse proxy (such as Caddy) on the VPS, which basically forwarded web requests to my home server. This works well for most things, although there was a definite performance hit by routing traffic through the extra hop.
By using the VPN connection, you wouldn't even need to open a port on your home network which is a great starting point for security as well.
view more: next ›
Worse plug how? You can buy DP cables without the locking mechanism.
Example