Worked eventually, was about DMZ on the router for my NAS
Allero
joined 2 years ago
Thanks! Syno one didn't work properly, but I got it to work through different means
Reachable through LAN, but not by URL, even if I port 81 to 81
P.S. Solved! NAS was sitting in the DMZ and this broke forwarding.
There's an issue with that first part. Do I configure it right? Should :8100 be redirected to 192.168.0.113:81 in this case?
Tried doing that - here's how I've set it up:
Expected behavior: now when I enter :8100, I reach 192.168.0.113:81
Real behavior: connection times out
I kinda see that they want to cover their asses a bit, but arbitration waivers as a whole should never be legal to begin with.
One should always be able to exercise their legal rights.
Some crypto, like Monero, is anonymous. Bitcoin/Ethereum is not.
In any case, if you use anonymous crypto, make sure to first sent it to a wallet (preferably with a subaddress in case of Monero), and then send it elsewhere.
I wonder if this could be solved on protocol level, i.e. automatically preserve objects with least redundancy, as known to the server.
Like if federated servers hold 50 copies of a file, it's likely not worthy of saving, but if there is only 1 or 2, it must be stored.
Federation would allow you to only host mods not hosted at other servers, with some level of redundancy.
Also, it could use a modding app with BitTorrent-like functionality, so that downloaders could share their copies as well.
Actually, I do - 81 is exactly the default port for nginx proxy manager. I just tried to expose it as a testing example, and already closed it back after a success (apparently port forwarding worked just fine, it's just that DMZ messed with it)
And since we're talking about this, what do I do with it next? I have it on my Pi, how do I ensure traffic is distributed through it as a reverse proxy? Do I need to expose ports 80 and 443 and then it would work automagically all by itself?