Max

joined 2 years ago
[–] Max@mander.xyz 1 points 2 years ago
 

This is a "Royal Dwarf" strain with a 365 nm LED flashlight shining on it.

[–] Max@mander.xyz 15 points 2 years ago

Genocide, xinjiang, camps,the, china

(Excellent tankie comment according to science)

[–] Max@mander.xyz 1 points 2 years ago (1 children)

(ironically) oyster meal 💀

off for a few days and then this honker popped up. So next round I’m doing only 10-15 minutes of fan per day. Maybe even less Good to know! I have some blocks almost fully colonized. I wonder if putting them to fruit in an open room (my living room) is already too much air flow for them.

[–] Max@mander.xyz 1 points 2 years ago

We need /c/infuratingasfuck

[–] Max@mander.xyz 2 points 2 years ago (1 children)

In that case, you’re better off just using the VPS machine as port forwarding port 443 to your home machine’s wireguard IP address and handle the SSL/TLS termination on the home machine.

This is what I would like to do! I was trying to handle the SSL termination 'automatically' by simply forwarding the connections to 443 of my machine's wireguard IP using nginx, but I did not manage to get it to work. That's when I found that I need to use something like 'stunnel' to handle the SSL termination. But I think that you may be suggesting an even simpler method of using port-forwarding instead of the reverse proxy. I am not sure how to achieve that, I will look into it using these terms.

[–] Max@mander.xyz 0 points 2 years ago (1 children)

ssh tunnels

There are so many concepts to learn about! But if the SSH tunnel improves the the available useful bandwidth compared nginx/wireguard, it might be worth looking into it too. Thanks!

[–] Max@mander.xyz 1 points 2 years ago (3 children)

Thanks a lot! This is kind of the configuration that I have converged to, with nginx and WireGuard. The last thing I need to set up correctly is for the SSL handshake to occur between the client and my home server, and not between the client and the internet-facing VPS, such that the information remains encrypted and unreadable to the VPS. The two strategies that I have seen can do this is SNI routing with nginx or to use stunnel. I still have not been able to set up either!

[–] Max@mander.xyz 4 points 2 years ago (3 children)

Wow! What is the substrate? Do you have any special tips for making them grow this large?

[–] Max@mander.xyz 5 points 2 years ago

What you can do is buy 2 plants and rotate them every week

What a good idea! I have a few potted sanseverias and I might experiment with a rotation like this one. I will feel a bit bad bringing one into the darkness while the others stay in the sun... But I have often thought that a plant would look nice in the bathroom.

[–] Max@mander.xyz 1 points 2 years ago

Oh, cool! I have managed to do it with the Wireguard tunnel! I set up a tunnel and use the nginx proxy_pass to redirect through the tunnel. It is pretty nifty that I don't even need to port-forward!

My next step is: in my current configuration, the SSL handshake occurs between the VPS and connecting client. So the VPS has access to everything that goes through... I need to figure out how to hand-shake through the tunnel such that the VPS does not get the SSL keys.

Thanks a lot for your suggestion!

[–] Max@mander.xyz 11 points 2 years ago* (last edited 2 years ago)

Sanseverias are quite resilient to low light and erratic watering, but I don't think any plant will "thrive" with little light. It will survive for a long time.

[–] Max@mander.xyz 1 points 2 years ago

Thanks! Wireguard was suggested as a VPN, and I am currently playing with that.

 

I have a nextcloud instance being hosted from my home network. The URL associated with it points directly at my home's IP. I don't want to host the instance on a VPS because disk space is expensive. So, instead, I want to point the URL at the VPS, and then somehow route the connection to my home's nextcloud instance without leaking my home's ip.

How might I go about doing this? Can this be achieved with nginx?

EDIT: Actually, not leaking my home's IP is not essential. It is acceptable if it is possible to determine the IP with some effort. What I really want is to be able to host multiple websites with my single home IP without those websites being obviously connected, and to avoid automatic bots constantly looking for vulnerabilities in my home network.

view more: next ›