You know whats funny... while I have Apollo installed - I always used Reddit's main app. :P LULZ - but I fully support them keeping their API open, as it has been for YEARS. I think they're fully out of line.
paulie420
LOL ; thank gosh I haven't seen that, yet... I hope LemmyNet continues to be developed and takes advantage of Reddit's ship jumpers.
I think its broken... or crumbling from the 10s of us trying to load page .P
Alright, I wanted to come back now that my setup is complete... special thanks to those of you who suggested nginx-proxy-manager - its very nicely put together and really makes reverse proxies a breeze...
Long story short, I just created a brand new VM... started with the proxy manager and built on top of that. Next up was my static Hugo website; it was too easy to point change Apache2's ports.conf to 8097 instead of 80, and use nginx-proxy-manager for the SSL certs... that one was basically plug and play.
The Bitwarden bit was a bit more involved, but not too bad... at first I just redirected traffic to the original (other machine) Bitwarden VM - but no one wants an extra VM to backup and support... so I went with a fork Docker of bitwarden_rs/vaultmaster - it comes w/ e-mail setup in the container, so one less thing to worry about... I had to swap around some docker-compose.yml ports and just point nginx-proxy-manager at it... this time, tho, I used the SSL certs from the docker; I didn't wanna dig in and remove what they already had running.
In the middle I was still fighting with myself and not taking ya'lls good suggestions - I tried to go the Cloudflared route; which is a cool service... but you can't tunnel root domains unless you're a paid user. Cloudflared tunnels would be great for exposing the Plex, TrueNAS, etc's of the world... but I didn't NEED/want subnets.
Thanks to the Beehaw community... TechHeart.life is up and running. :P (Don't worry, the Bitwarden is on a private domain. Phhhbbbbtttt.)
Everyone here is awesome for ALL the replies. :P Thank you!!
I decided to try a Cloudflared tunnel, but that didn't work out because I can't get the main domain1.com domain to go thru the tunnel... only 'apps', like blog.domain1.com. :P
And, I'm still ironing out how to pass nginx to another local IP on my network; I just haven't gotten it to click yet. All the info needed is right here - I promise to come back when I iron out the setup and post how I managed to do it...
I can figure out how to pass nginx [or apache2, for that matter] to another PORT on the same local IP - I think I have both domains listening on ports 80/443 - and I'll have to change that in order to route the data correctly... let alone getting out to another local IP.
Again appreciate all the info - sometimes I just have to learn a bit more since I have all the documents right here. :P
Agreed - I don't think I've been on a Tornado BBS software; but I still code in Mystic BBS's PASCAL-like MPL language. :P
damnit! :P
Hold my beer! LEMMINGS
I only know enough code to break things, but I wouldn't mind working on some documentation - I'll go read what Lemmy needs; thanks for reminding me that anyone can chip in.
Heck yea, I am a retro enthusiast. I currently have a PiBoy DMG running emulation staion and a customized version of Raspberry Pi OS w/ joycon and buttons mapped to a mouse emulation - its a nice form factor for having a portable Linux-box in the field... I still get looks when I whip out a 'gameboy' to do some actual work. :P
I stick to mostly 8bit and 16bit platforms, so the Pi 4 is more than enough for me...
I also have a few retro computer setups; of course, a C=128 for all my Commodore needs - an Apple g4 basketball w/ MacOS 9 - an antique Philco Predicta television that runs both some Python script for random vintage videos, and can serve up PONG - I retrofitted an old PONG controller w/ a Pi Pico so it feels right.
I have a couple other machines that bring me back to the 486 MS-DOS days. :P
Nice to know theres other folks that are into this hobby - cheers!
LOL... it'll be easy, I tell ya!
So I dove in this afternoon, thinking I had all the info I needed to easily get a setup w0rking... I changed my port forwards to the domain2.com machine - the one running apache2 on a webiste; leaving the bitwarden.domain1.com not seeing traffic. Then, I created a new virtual host file on the domain2.com machine;
cat bitwarden.domain1.com.conf
<VirtualHost *:80>
ServerName bitwarden.domain1.com
ProxyPass / http://10.0.0.155/ nocanon
ProxyPassReverse / http://10.0.0.155/
ServerAdmin paulie420@domain1.com
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =bitwarden.domain1.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
And ran certbot to get https certs - certification would only be on the domain2.com machine; all proxied data would be sent over http, but I figured that was OK as its just me accessing the domain1.com service.
BUT alas, the setup didn't work; I have some suspicions... bitwarden is running inside a docker container, so... I dunno if that has something to do with how its listening, and its running nginx; what I thought was that apache2 would simply send all traffic from the bitwarden.domain1.com domain over to my local IP 10.0.0.155 machine and that machine would just pick it up simple pimple and display to the user going to that domain. Another thought - maybe its because Docker/Bitwarden HAS https in that container - ohhhh, thats a thought; however it still didn't function correctly before I ran certbot on the domain2.com setup.
UGH... more to come - I'm trying options. :/ Grrrrrr. :P
PS; posting code in Lemmy doesn't work so great, does it? I used a backtick but didn't get the results I'm accustomed to...
I like the Fediverse b/c its more connected than our old forums of yesteryear, but without big tech breathing down out necks...