icedterminal

It’s an industry security standard. Not a defect. If you don’t agree with it, fork the software and modify it to suit your needs.

Some self hosted services refuse to work if you use a self signed certificate with your public facing IP. They only allow self signed certificates when using one of the handful of private addresses.

Some apps on mobile devices for the service you use won’t work unless a trusted certificate is used. A self signed certificate behind the scenes creates an error that isn’t handled and you can’t connect.

You lose the ability to have a proxy in front to handle abuse so your server is spared the headache. You need a domain to do this.

TLS.

While technically you can use TLS with a self signed certificate, it creates additional problems with a public facing service. Only recommended for internal services.

You either set the DNS settings per device to the system running PiHole / AdGuard Home, or if your router allows, set the DNS there. It’s ideal to set it on the router.

Any time a device makes a DNS request to a domain, it’s checked against the list. If found, it’s stopped. If not found, it gets sent upstream to your choice of a public DNS configured during setup. I use Cloudflare (1.1.1.1, 1.0.0.1).

Exactly. The alias just points to the script which is executed.

After the user mentioned it , I looked it up. It’s all over Apple’s supper threads. Hilariously, there’s an old reddit thread about it

https://discussions.apple.com/thread/253838180

https://superuser.com/questions/317900/eliminate-macbook-capslock-delay

https://www.reddit.com/r/macbook/comments/o6q52c/mba_m1_caps_lock_key_delay/

That’s even worse IMO. Lol.

macOS has a caps lock timeout? The fuck…

At one point they offered unlimited storage for Play Music only. You could literally upload your entire collection. They changed it later to consume your Drive storage. Cheap enough plans so I subscribed. Then they killed off Play Music. I’m still salty about that.

but the containers are still running as root, as the daemon itself raises the access to root.

No. The daemon can run without root, as such the containers don’t have root. My docker install doesn’t have root access. None of my stacks / containers need any root access tbh. I don’t have any troubles with deplyong stuff.

https://docs.docker.com/engine/security/rootless/

This information reflects the current contract terms Verizon offers to everyone.

iPhone is $899 + tax. Verizon pays Apple what you pay for the iPhone. You sign a contract for 36 months that states you’ll pay Verizon a monthly installment without interest.

As for the “free” phone, it really can be free. Based on their own internal metrics is what makes you eligible. Accounts the system has flagged for fear of losing (retention), good standing (no missed payments), long time customers (loyalty), new customers, or when there is an abundance of stock and a new model is set to release. The catch is that you’re on the hook for the price of the phone if you upgrade early or want to cancel your line. The average rep is not letting you upgrade because the system says no. A manager can override but if they do, you lose the credit. Your next bill will include the price of the phone. They’re still making money off you in the long term whether or not the phone is free. It’s calculated business.

Pg has significantly better performance in a smaller self hosted environment. Notably because you’re doing a balance of reading and writing, or mostly writing since data changes regularly. For large scale operations where reading data is the primary use, MariaDB/MySQL is faster.

You should for sure move away from a proprietary OS. There are many ways to go about it. I personally use Arch minimal with hardened kernel. Everything runs in non-root docker containers. Commonly used distros are Ubuntu and Fedora. But there are many more to choose from. https://distrowatch.com/search.php?category=Server

To bypass their CDN (referred to caching) you need to setup a Page Rule for the entire Plex domain.

https://developers.cloudflare.com/support/page-rules/how-do-i-include-or-exclude-a-specific-url-from-cloudflares-page-rules/

Cache Level set to Bypass for https://plex.mydomain.me/*

Thanks for the information. Although Argo still greatly reduces latency if a user cares to reduce communication time.

Once you agree to letting friends and family access your hosted services, you become the tech support for any problems. Whether that be your fault, user error, etc. You should absolutely limit who you give access to. In my case, only three people can and that’s immediate family. No friends, no extended family. I don’t wanna deal with all that mess when I deal with it at work. Don’t over extend yourself by being nice.

Using Cloudflare is against the ToS when used for services like Jellyfin. Your account can be limited, closed, or find yourself getting a several hundred dollar bill for data usage because you’ve breached the terms of service. Additionally, streaming content on free accounts incurs higher latency which I’ve confirmed myself Argo smart routing massively reduces. https://github.com/jellyfin/jellyfin/issues/9295 - Don’t abuse what’s free or you may lose it.

Google shouldn’t be indexing your domains anyway. If it’s flagged your domain, it’s been indexed and scanned. Alternatively, it could indicate you have a weak point somewhere on your server and you’ve been breached. Google’s scan picked up whatever it was. Though I doubt this is the case and just a false positive. Double check your robots.txt files and disallow everything. Most index bots respect this. You can use a community sourced bot blocker. https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker

I’ve been running my own self hosted services for almost a decade. Though I have a background in IT directly doing this kind of stuff daily at work. As long as you have a strong firewall, modern TLS, relevant security headers, automatic tools like fail2ban, and have a strong grasp on permissions, you should be fine. Before I moved everything to non-root docker, it was given its own service user and SELinux policy. Using direct DNS isn’t so much of a problem. You shouldn’t have any issues. Feel free to reach out if you have any questions.