@NerdyDad Both HP and Dell make what you are looking for. I'd stick with them just based on my experience. Hope yopu find what you are looking for.

@NerdyDad If it's only for web access I'd just order minimal specs. How many are you ordering? The protection plans from Dell are actually great. I had a customer awhile ago that was an intermediate school who broke them constantly and probably 5 a week needed to go out for repair. Very reasonable price imo.

@NerdyDad Does this have to be laptop-like?

@dafyre said in Anyone using Jitsi behind Nginx:

This might be overcomplicating things... but what about setting it up behind an nginx setup on the same server as jitsi, and then use your main nginx proxy to forward to the jitsi nginx?

Why would that work vs. the normal reverse proxy? If you have a problem and make two of the same problem it doesn't solve the issue I would think. I'm actually asking, not being a dick.

It may be that mine was the same. Only ever tested it with one user.

Happy Birthday @DustinB3403 !

Doesn't jitsi require the use of websockets? I think I used them when I tested it but I'm not 100%

Playing Don't Starve Together again with a group of 4. Great game. Was on sale for $6 and it just can't be beat for that amount of money.

In Certbot 0.28.0 (the November 2018 release), Certbot will begin to prefer the HTTP-01 challenge type to the TLS-SNI-01 challenge type when both are available.

Users who first obtained a certificate for their domain before January 2018 and have not changed the account they use to issue certificates for those domains may encounter issues when Certbot attempts to automatically renew their certificates.

Certificates obtained for other domains since then have already been using the HTTP-01 validation method for initial issuance, and are unlikely to encounter new issues from this change.

The Certbot team recommends that users test manually from the command line in advance of certificate expiry. To use the HTTP-01 challenge type regardless of Certbot version, add the flag --preferred-challenges http-01,dns-01 at the command line.

For example:

certbot renew --dry-run --preferred-challenges http-01,dns-01

Users encountering errors may need to fix their firewall settings to allow incoming connections on port 80. Some resources about configuring a firewall are available here 2 for Debian and Ubuntu users, here for CentOS 7 users, and here for other Linux users.

Between November and February (when the TLS-SNI-01 challenge type is deprecated at the server end 4), users who have been relying on TLS-SNI-01 can use the flag --preferred-challenges tls-sni-01 as a temporary patch to get a certificate quickly, before correcting the configuration.

Received this error when trying to renew my LE cert via Certbot

Incorrect validation certificate for tls-sni-01 challenge.

From Certbot's website:

"Under the hood, plugins use one of several ACME protocol challenges to prove you control a domain. The options are http-01 (which uses port 80), tls-sni-01 (port 443) and dns-01 (requiring configuration of a DNS server on port 53, though that’s often not the same machine as your webserver). A few plugins support more than one challenge type, in which case you can choose one with --preferred-challenges."

sudo certbot renew --preferred-challenges http worked. My question is, is just an http challenge the correct way to do this?