paulie420, 1 year ago

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...