Well, this is in JS to be clear

Instead of

const name = user.name

It’s

const userToName(user) => user.name;

const name = userToName(user);

Ad nauseum.

We have a principal engineer on our team that is pushing this sort of style, hard.

It’s essentially obfuscation, no one else on the team can really review, nevermind understand and maintain what they write. It’s all just functional abstractions on top of abstractions, every little thing is a function, even property/field access is extracted out to a function instead of just… Using dot notation like a normal person.

Even better, it’s now a nice database of who companies and governments can go after when they want or need to!

Let’s not mention the abysmal performance for servers. Making it largely infeasible to scale.

It’s not the solution, not even remotely close, unfortunately.

Definitely not tube archivist…

Development is semi-frozen. The developer is also more hostile and they need to be even to contributions from others.

And it does not store your files in a way that is self-contained. And there is no option to control the naming or organization of the files it stores.

Your file system should be navigatable and understandable without having to run software and pull information from a database in order to interpret it. Tube Archivist is far FAR from ideal media archival software IMHO.

It misses the mark in so many ways it drives me insane.

Except that relay nodes often get out onto proxy lists.

Which means you now get to solve capchas for absoluty f-ing everything now.

Cool, lots of information provided!

Nice to see that you never have to go far to find the dismissive toxicity of the Linux community no matter the platform.

It costs nothing to say nothing, when all you have is… Whatever you call this.

This is the way.

I do this. PFsense DNS resolver, and have loopback enabled.

DNS for all the domains points at a reverse proxy (Caddy) that handles valid HTTPS termination. So all my services have valid HTTPS certs, and devices on my network can access them normally.

Way too much for sure.

Just the business internet to get the foot in the door for a static IP 5x’s the cost of my Internet.

It’s actually cheaper to just have DC IPs and proxy through hosted containers. Which is kind of crazy.

Negative aspect is that DC IPs aren’t treated very nice.

It’s frozen for features and changes. Even bugs & issues are shrugged off and closed unless they are big. PRs from others as well I’ve seen.

The maintainer is semi active, but they’re kind of a dick, and tend to minimize problems and downplay others in ways that are borderline toxic.

It’s a shame :/

Guessing it’s not a dead/halted project?

The Reddit space is just a bunch of pictures of people’s home Labs it’s not really a self-hosted community at all.

It’s not interesting to explore and read like this one is.

It’s suffered from a common phenomena of any community that grows in popularity where it caters to the lowest common denominator and loses its niche.

I didn’t really mention immich directly here.

This is a problem which is endemic to casual software development like many FOSS projects. It’s a reality of how free software tends to be built in general vs commercial software.

The issue here is that these are solvable problems, release compat isn’t a new problem. It’s just a problem that takes dedicated effort to solve for, just like any other feature.

This is something FOSS apps tend to lack simply due to the nature of how contributions tend to work for free software. Which is an unfortunate reality, but a reality none the less.

People really underestimate the value of stability and predictability.

There are some amazing FOSS projects out there ran by folks who don’t give a crap about stability or the art of user experience. It holds them back, and unfortunately helps drive a fragmented ecosystem where we get 2,3,5 major projects all trying to do the same thing.

Because the majority of my traffic and services are internal with internal DNS? And I want valid HTTPS certs for them, without exposing my IP in the DNS for those A records.

If I don’t care about leaking my IP in my a records then this is pretty easy. However I don’t want to do this for various reasons. One of those being that I engage in security related activities and have no desire to put myself at risk by leaking.

Even services that I exposed to the internet I still don’t want to have my local network traffic go to the internet and back when there is no need for that. SSL termination at my own internal proxy solves that problem.

I now have this working by using the cloudflare DNS ACME challenge. Those services which I exposed to the internet cloudflare is providing https termination for, cloudflare is then communicating with my proxy which also provides https termination. My internal communication with those services is terminated at my proxy.

I stated in the OP that this is off :/

I stated in the OP that cloudflair HTTPS is off :/

I’m not using cloudflare for the certificate. I also can’t use the cloud for certificate anyways for internal services through a loopback.

Similarly you can have SSL termination at multiple layers. That’s works I have services that proxy through multiple SSL terminations. The issue that I’m having is that the ACME challenge seems to be having issues, these issues are documented and explained in various GitHub threads, however the set of solutions are seemingly different and convoluted for different environments.

This is why I’m asking this question here after having done a reasonable amount of research and trial and error.

I am doing SSL termination at the handoff which is the caddy proxy. My internal servers have their SSL terminated at caddy, my traffic does not go to the internet… It loops back from my router to my internal Network.

However DNS still needs to have subdomains in order to get those certificates, this cloudflair DNS. I do not want my IP to be associated with the subdomains, thus exposing it, therefore cloudflair proxy.

You’re seeing the errors because the proxy backend is being told to speak HTTPS with Caddy, and it doesn’t work like that.

You can have SSL termination at multiple points. Cloudflare can do SSL termination and Cloudflair can also connect to your proxy which also has SSL termination. This is allowed, this works, I have services that do this already. You can have SSL termination at every hop if you want, with different certificates.

That said, I have cloudflair SSL off, as stated in the OP. Cloudflare is not providing a cert, nor is it trying to communicate with my proxy via HTTPS.

Contrary to your statement about this not working that way, cloudflair has no issues proxying to my proxy where I already have valid certs. Or even self signed ones, or even no certs. The only thing that doesn’t work is the ACME challenge…

Edit: I have now solved this by using Cloudflair DNS ACME challenge. Cloudflair SSL turned back on. Everything works as expected now, I can have external clients terminate SSL at cloudflair, cloudflair communicate with my proxy through HTTPS, and have internal clients terminate SSL at caddy.