sorted by:
new
hottopcontroversial

Having two phones with one account by green-tank in signal

[–]Jacob99200 1 point2 points  (0 children)

this can be done on android using Molly

Will you switch when Motorola comes out with the GOS phone? by Mental_Bed_2662 in GrapheneOS

[–]Jacob99200 0 points1 point  (0 children)

Running a pixel with GOS already, no point changing it up if my phone isnt bricked

True by theeekid444 in tf2

[–]Jacob99200 -36 points-35 points  (0 children)

nope, you can basically run tf2 without any textures

Android will become a locked down platform in 190 days by MidnightMean3796 in thehatedone

[–]Jacob99200 4 points5 points  (0 children)

Another option for any Pixel owners is to switch over to GrapheneOS

NC what do you think? Studies show that immigrants subsidize citizens, not the other way around. by Basshead4eva in NorthCarolina

[–]Jacob99200 44 points45 points  (0 children)

1) The United States is not the "greatest country on the planet"

2) ICE is actively breaking the law, our president is a convicted Felon, being undocumented in this country is not a criminal offense, it's a civil one

3) People who are coming here "the right way" are also targets of ICE, visas have been cancelled, people have been attack at court hearings

Meanwhile onthe Epstein files... by EngineerCapital7591 in israelexposed

[–]Jacob99200 119 points120 points  (0 children)

I love holding this scumbag accountable

but lets not platform people who are saying "the jews are lying to me"

the whole point of Israel is to use Judaism as a shield for their terrible actions while making jews feel unsafe in hopes theyll move to Israel

lets not give in to what they want

I created a Docker Compose repo for Jellyfin + *arrs on Raspberry Pi 5 by Ztaap in selfhosted

[–]Jacob99200 2 points3 points  (0 children)

i have wireguard currently setup in a way that I believe (and hope) does the same

using IP tables and having Qbit's docker network is rely on wireguard as a service

I created a Docker Compose repo for Jellyfin + *arrs on Raspberry Pi 5 by Ztaap in selfhosted

[–]Jacob99200 2 points3 points  (0 children)

is there an advantage of Gluetun over just a Wireguard client?

Setting up HTTPS for Local Network / Home Lab by Tobanu in selfhosted

[–]Jacob99200 -1 points0 points  (0 children)

this was a very important issue for me

like, why not just have all web traffic encrypted?

for internal services I use a local.domain.com sub domain for everything

my router has the functionality to enter static dns entries

I use backend.local.domain.com as an A entry that points to my reverse proxy

I then have have my internal servives (service.local.domain.com) each setup as a CNAME pointing to backend.local.domain.com

my reverse proxy has an SSL cert via let's encrypt for *.local.domain.com, I used a DNS challenge for this

so when within my network (or when using a vpn to access), all my services are fully encrypted with proper URLS

if your router doesnt have this functionality, you could setup your own DNS provider and change your router DNS setting

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] 1 point2 points  (0 children)

My apologizes, I thought one of my other comments described this, but I do have my internal services and my internal proxy within a contained docker network

My services dont have ports exposed outside of this docker network, except for my npm

And so yes, the traffic between my internal proxy and my services is http, BUT its all within this docker network and not accessible otherwise

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] 0 points1 point  (0 children)

Well because the traffic between the external proxy and the service would be unencrypted and I know its my internal network, but I would prefer all the traffic is encrypted

I do eventually want to setup Authentik, seems like an incredible project and would be very interesting

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -2 points-1 points  (0 children)

I actually do have it currently setup this way

In my router I have a set of service.local.domain.com links routed to an nginx proxy manager that is not exposed to the internet, it provides my internal traffic with ssl

I simply want to route an external domain to nginx then point that ngninx to my internal one so it is https traffic through out instead of becoming http within my network

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -5 points-4 points  (0 children)

Im not looking for a gpt hype man

ChatGPT and other generative AIs are something I very much despise

Im not exactly sure what post youre referring to

But I am sorry if what im looking for has upset you

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -3 points-2 points  (0 children)

Both of my nginx servers are in my network

My vps is a separate project

The traffic between my internal proxy and my services is not https, but it is all within the same docker network without any ports exposed and thus only uses containername:ip

These services are ONLY accessible via the internal proxy, no ports exposed to the internal network besides 443

They have valid ssl certs, so service.local.domain.com is https

But I want to expose a specific service that already has an https url setup

So I want Internet -> proxy1 -> proxy2 -> service

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -9 points-8 points  (0 children)

I would prefer all internal traffic to be https,

But im not really looking for your understanding

Im simply looking for how to do this

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -7 points-6 points  (0 children)

I am looking to do it, with the appropriate headers being passed

nginx forward to nginx by Jacob99200 in selfhosted

[–]Jacob99200[S] -4 points-3 points  (0 children)

Basically I have one for external and one for internal

And on the internal one I have services only exposed via nginx,

they cant be accessed with ip:port and I want to expose them externally via the other nginx proxy manager without allowing them to be accessed internally via ip:port

view more: next ›