So a ream of paper is 500 sheets. You’ll be able to search better by looking for the weight of the paper per ream, rather than the thickness.
https://thomasgroupprinting.com/how-is-paper-weight-measured/
Copier paper is likely to be a bit thinner than letter paper.
Careful about going too thin, or your printer will just shred it and jam up. Tissue paper for example is unlikely to work. Newsprint paper might be okay, but you’ll need to look at the numbers.
Yup, that’s a really good pattern to follow. Not only does it minimize your exposure behind a secured entry, it also makes sure that all of your access is uniformly authenticated.
You have to do some shenanigans to do something similar with other, non-http based services, but it’s possible with most of them.
It’s not a simple task, so I won’t list many specifics, but more general principles.
First, some specifics:
Generally:
You mentioned using cloud flare, which is good. You might also consider configuring your firewall to disallow outbound connections to your local network. That way if your server gets owned, they can’t poke other things on your network.
Honestly, cost wise you should just buy a cheap refurbished desktop with similar specs.
It’s in the name. Copyright. As in, the right to make a copy.
It’s perfectly legal to sell a digital good as long as you don’t retain it as well.
It’s illegal to make a copy of a book and then sell that copy.
From probably the most biased source possible: https://copyrightalliance.org/education/copyright-law-explained/limitations-on-a-copyright-owners-rights/first-sale-exceptions-copyright/
As they point out, most digital works are licensed, not sold, so there are terms and conditions associated with how you can use them.
So it’s perfectly consistent, just grossly out of date for it’s intended purpose of “make sure writers can make money selling their books without worrying that getting copies made will be pointless because someone else will undercut them and leave them with 1000 prepaid copies of their book that everyone bought cheaper”.
We should have a system that preserves that original intent of “creators get compensated”, without it turning into our culture gets owned by some random company for more than a lifetime.
Protip: The ‘B’ is RAID stands for “backup”.
So, you’re going to run into some difficulties because a lot of what you’re dealing with is, I think, specific to casaOS, which makes it harder to know what’s actually happening.
The way you’ve phrased the question makes it seem like you’re following a more conventional path.
It sounds like maybe you’ve configured your public traffic to route to the nginx proxy manager interface instead of to nginx itself.
Instead of having your router send traffic on 80/443 to 81, try having it send the traffic to 80/443, which should be being listened to by nginx.
Systems that promise to manage everything for you are great for getting started fast, but they have the unfortunate side effect of making it so you don’t actually know what it’s doing, or what you have running to manage everything. It can make asking for help a lot harder.
You’ll be fine enough as long as you enable MFA on your Nas, and ideally configure it so that anything “fun”, like administrative controls or remote access, are only available on the local network.
Synology has sensible defaults for security, for the most part. Make sure you have automated updates enabled, even for minor updates, and ensure it’s configured to block multiple failed login attempts.
You’re probably not going to get hackerman poking at your stuff, but you’ll get bots trying to ssh in, and login to the WordPress admin console, even if you’re not using WordPress.
A good rule of thumb for securing computers is to minimize access/privilege/connectivity.
Lock everything down as far as you can, turn off everything that makes it possible to access it, and enable every tool for keeping people out or dissuading attackers.
Now you can enable port 443 on your Nas to be publicly available, and only that port because you don’t need anything else.
You can enable your router to forward only port 443 to your Nas.
It feels silly to say, but sometimes people think “my firewall is getting in the way, I’ll turn it off”, or “this one user needs read access to one file, so I’ll give read/write/execute privileges to every user in the system to this folder and every subfolder”.
So as long as you’re basically sensible and use the tools available, you should be fine.
You’ll still poop a little the first time you see that 800 bots tried to break in. Just remember that they’re doing that now, there’s just nothing listening to write down that they tried.
However, the person who suggested putting cloudflare in front of GitHub pages and using something like Hugo is a great example of “opening as few holes as possible”, and “using the tools available”.
It’s what I do for my static sites, like my recipes and stuff.
You can get a GitHub action configured that’ll compile the site and deploy it whenever a commit happens, which is nice.
Vpns and casting create a complicated network situation sometimes. Without being able to see exactly what was going on, it can be difficult to tell what’s happening.
Sometimes casting involves sending the data from the controller, your laptop, to the renderer, your TV. That means you laptop pulls the data down and then forwards it.
Sometimes it involves telling the renderer how to get the data so that it can pull it down and play it.
When you use a VPN, you’re sending your traffic through a tunnel so that it’s “outside” your local network. There will be some exceptions for certain local behavior that needs to be local, unless you configured it not to but you probably didn’t.
It’s honestly curious that it ever works, since the VPN should make it so you’re basically “not there”, and so casting shouldn’t be possible.
My recommendation would be to use Plex if it works.
Download on the VPN and then drop off to cast it is an alternative.
There’s enough moving parts that you’re not going to have any fun figuring it out, and the answer will probably be something you can’t fix.
I would use something like wireguard, or another VPN service you can host yourself if your router supports it natively.
From the looks of it Minecraft servers seem to have dogshit authentication, so using some form of private network setup is going to be your best move.