fully backwards compatible
Kinky. I like it.
fully backwards compatible
Kinky. I like it.
Assuming your local service is accessible from the nginx server, you can proxy the request to it:
server {
listen 80;
location / {
proxy_pass http://10.100.100.2:3000/;
}
}
…where 10.100.100.2
is your local IP on the VPN and 3000
is the local port your service is listening on, and 80
is the public port your nginx server listens on. Everything that hits your nginx server at http://yourserver.com:80/
will proxy back to your local service at http://10.100.100.2:3000/
. Depending on what you’re hosting, you may need to add some things to the config.
I’m assuming that you are trying to proxy an http web server. If not, you’re going to have a hard time with nginx. Can you post your nginx config? Are you getting any response from nginx at all?
…he should do anti-gravity next.
There’s a python library for that.
True story:
alias ipa='ip a'
It has space for a standard PSU inside, but I’m pretty happy with this one:
https://www.amazon.com/dp/B0785GRMPG
I’ve been running it for about 4 years now.
If you have a fat GPU, you might have trouble with additional PCIe cards. You’ll definitely need more cooling as it only comes with one tiny fan.
Just Quit Uploading Everything Ridiculous, Y’all
It’s not DNS.
There’s no way it’s DNS.
It was DNS.
-SSBroski
Did you set the UPLOAD_LOCATION
variable in your .env
file?
Same.
PHaPpers
I like cryfs for this purpose:
Kubernetes? I’ve never even seen her netes.
The need to transcode has nothing to do with location. It has everything to do with the codec support on the client.
Some servers blacklist you even if you have DMARC, SPF, DKIM, DNS setup perfectly, but your IP is in a block of addresses that may or may not have been hosted by the same ISP of some unrelated server that was possibly compromised 10 years before you even set up the mail server. Ask me how I know.
Wait, so you backup your backups? Why not just 2 backups of the same thing?
That’s what Emby thought.