I like it :) Can you provide a link to the sensors you used?

You‘re supposed to host this yourself.

Set the DNS cache time to 60 seconds.

Set the script to run on every host delayed by some time to avoid simultaneously accessing the API (e.g. run the script every other minute).

With this approach, you get automatic failover in at most 3 minutes.

I’d host it on both webservers. The script sets the A record to all the servers that are online. Obviously, the script als has to check it’s own service.

It seems a little hacky though, for a business use case I would use another approach.

OP said that they have a static website, this eliminates the need for session sync.

Your challenge is that you need a loadbalancer. By hosting the loadbalancer yourself (e.g. on a VPS), you could also host your websites directly there…

My approach would be DNS-based. You can have multiple DNS A records, and the client picks one of them. With a little script you could remove one of the A Records of that server goes down. This way, you wouldn’t need a central hardware.

No USB power plug operates at 5 V when providing 65 Watts. That would be 13 Amps. Both power plugs most likey use 15 or 20 volts internally. 19 volts is not allowed over USB.

Edit: Here is a short summary of the USB-PD spec from Wikipedia

For a start, try hosting something in your own home. A raspberry or an older PC or laptop should be enough.

My first projects were a print server (so I can print via wifi) and a file server. Try to find something that is useful for you.

Only start hosting on the internet when you’ve learned the basics and have more experience.

As for me, I just visit this site to see the next sales. But it’s a neat idea

I agree, but I understood this question in the context of a homelab.

And for me, a homelab is not the right place for a public website, for the reasons I mentioned.

No, with these reasons:

• Bandwidth isn’t plenty
• My “uptime” at home isn’t great
• No redundant hardware, even a simple mainboard defect would take a while to replace

I have a VPS for these tasks, and I host a few sites for friends amd family.

You’re right, Google released their vision in 2023, here is what it says regarding lifespan:

a reduction of TLS server authentication subscriber certificate maximum validity from 398 days to 90 days. Reducing certificate lifetime encourages automation and the adoption of practices that will drive the ecosystem away from baroque, time-consuming, and error-prone issuance processes. These changes will allow for faster adoption of emerging security capabilities and best practices, and promote the agility required to transition the ecosystem to quantum-resistant algorithms quickly. Decreasing certificate lifetime will also reduce ecosystem reliance on “broken” revocation checking solutions that cannot fail-closed and, in turn, offer incomplete protection. Additionally, shorter-lived certificates will decrease the impact of unexpected Certificate Transparency Log disqualifications.

Sorry, I understood you wrong. You’re right!

Nothing of value was lost when EV certificates disappeared.

even more secure with the 90 days policy.

Yes, if you do this manually it will work.

I meant certbot with nginx plugin and http-01 challenge.

You’re right, ssl.com offers this, too.

IMO, sticking to manual processes that are error-prone is a waste of money and not a sign of a honest business.

Yes, it can be easier. But not every DNS provider allows API access, so you might need to change the provider.

(good luck with that in many enterprise scenarios).