OK I understood that the request came from internet and tailscale was to link the reverse proxy and the server.
In this case try ipv6, pretty sure you have ipv6 and you will have a public address.
But for this case you will need a dns in your network so example.com can be resolved and then your proxy will make the right request.
Yes doable.
Yes, it is possible, but you need a domain (example.com) that I guess you want to be resolved from internet and a public face ip.
After that, yep, if the reverse proxy can resolve tailscale names (basically it has tailscale installed in the same machine) and the service is reachable via tailscale, then it is perfect.
In fact in my setup I have a public domain name that is translated into a private domain name in the reverse proxy (exactly what you want with the addition of tailscale)
It is almost impossible to achieve those numbers, specially the idle, and the load we can only to be close to them when we use the watt/ per-useful-instruction metric.
recentest hw will have decent idle consumption (n95 is around 2w) but the rest of the hw will consume more and usually you attach more powerful/energy hungry devices so expect <10w in idle and perhaps <25w under load.
Older hw could not be so bad under load but they will idle less and will consume more
Start with a nas, the rest will naturally come when you try to access your data for outside, or organize your data, or save more data types to your nas.
Your nas should be the central device and you build the rest around it.
Now, The question is, which nas? I would recommend synology, they are not too performance, a bit expensive and the company is lately doing suspicious moves, but the sw and the hw are rock solid and they are quite good for beginners from almost all angles. Extra point for how many howtos and tutorials are present in internet.
Once you are comfortable with them, you will realize the rest
How, because Overton window says the opposite
Thanks for the answers
Interesting, thanks.
Last question, is it necessary to have the safety/ standard compliance certified by an external authority? If yes, how is it done? Same for the sw/FW updates
And no safety regulation? No CE marking, no refuse to operate if the gnd line is not well established, no gracefully fail without degrading the safety?
Edit: fast Google search returns several iec (62955), CE marking, and some other low power directives (this is country dependent) which may be enforced via Sw.
I don’t know OP, I am by no mean an expert, but I would spend a bit of time navigating for the terrible passionating world of regulations and directives :(
What are the certifications of that thing?
I mean, I guess it is a 11kw line, there are a few things that the system needs to fulfill about the regulation.
How are those things done?
OK, I’ll take a look
Should I give it a try?
I’ve seen things… Near the gate of Tannhäuser, things you little people wouldn’t believe.
And I am not joking…
How is the i2p doing?
Last time I checked (several years ago) it was slow, non performing and scarce in results.
And my lack of knowledge didn’t help at all :)
By any chance… Your proxmox is not close to any source of big electromagnetic fields, right?
Close to big Transformator or electric motors, right?
OK, it is clearer now, thanks
If I get it correctly, this is a kind of kasm but only for the local user, right?
Yep, at least for their own internal mistake. I rebooted them a few times in that time because updates and important config updates. Even for power outages (2 iirc) they are resilient, they are set to automatic boot up when the power is back.
It didn’t happen in more than 5 years…
For critical equipment you need to spend the extra dollar to minimize this kind of stuff
I see, well if borg really ticks all checkbox es and you know how to use it I would explore any further.
Sincerely, borgbackup is really a top solution with a lot of nice features
Nginx is considered battle tested.
Very few products have this level of puic scrutiny and and a good record of being safe.
Once this is said, the majority of problems come from misconfigurations, so triple check the things