It’s even better when the English word is so riddled with vowel syllabics that Japanese phonemes require that it wraps all the way around and becomes unrecognizable…even when it’s “English.” My fav: Makkudonarudo - マックドナルド even tho most people just call it “Maku-do” for McDonalds.

Also, gotta watch out… just when you think “Pants” is just “Pantsu” you actually just said “underwear” in Japanese.

Dems prove once again that they have NO IDEA how to represent the people who voted for them… or even just like, make themselves even slightly likable.

Yeah, had to go touch grass after having this drive me crazy for a second day. The reverse proxy is “working” according to caddy… and the DNS is all pointed in the right spots but it just wont go. The CasaOS is the only think I can think of too. CasaOS is just a frontend GUI for a headless server… easy to manage/move media files, etc. INstalls docker containers with a click. I will have to try doing Caddy as a docker and see what happens.

To answer your question, if I put in the publicip and port, I get my Jellyfin, it’s reaching them, and working just fine. Just can’t get my DNS pointers to be recognized/used by Caddy. I’ve tried two different domains at this point. Whatever. Infuriating, but whatever. My shit still works. Thanks for trying. I tried to use the Caddy forum but they literally make you format/type your whole issue in predesignated HTML and shit… I typed the whole thing out but I don’t know shit about HTML so the ‘issue’ showed up as blank. Fuck this. I can live without.

I’ve tried this caddyfile version and one above, for both, I get “Problem loading page. Secure connection failed. Internal error.” Oddly, I get the ‘welcome to caddy’ page directly at my IP but at my sub domain I get the error.

unfortunately, it’s still not working. “Problem loading page. Secure connection failed”

Thanks very much, this is really helpful… one thing I note is that I don’t know what “api.example.com” is … is that necessary to make this work or is it just an option? I haven’t mucked with API of Caddy at all…do I need to?

ugh. no. Now caddy wont start… various errors… sometimes it says listening port 80, port 80 in use. This morning after reset and caddy fmt --overwrite, it says: Error: loading initial config: loading new config: http app module: start: listening on :443: listen tcp :443: bind: permission denied Error: caddy process exited with error: exit status 1

do you want config.php from Caddy or the docker compose?

ooh I broke it as I was trying things and this was solid gold… thank you stranger!

Hey thanks for addressing that. So yes, I have my local ip as a subnet… you’re saying that means i don’t necessarily need the tailnet IPv4 as my pointer?

So, it sounds like you’re staying if I want all my services (jellyfin, nextcloud, etc) behind ONE reverse proxy/https then the easier method is to install Caddy as docker and use the containername:containerport method?.. did I understand correctly? Thanks

My caddyfile is just

sub.mydomain.com {

reverse_proxy my.server.ip.address:8097

}

lol … obviously I annonymized it for this copypaste, but you get the idea… I am probably missing some things.

I see the welcome page in the image above