App Proxy http and https pass thru

[Nozy]

Hi All

Sure I not downing something right but sure I missing something
I know I can setup a app proxy but I have some service that need http to get ssl working and the app prox do both ( can't see it )

it Bitwarden ISP > Proxy https only > server so it it need to get a new SSL key it will not work so I have to get the firewall do change the this docker server for both let it up date and change it back to the cloudron server

Michael

[james]

Hello @nozy

I am very confused by your topic and can't really make out what you are doing, trying to do or what the goal is.
Could you please describe what you are trying to do in detail?

[nebulon]

I was also scratching my head a bit and tried various app proxy setups to see what I miss. @nozy maybe you can explain a bit more what you aim is?

[Nozy]

yep sorry was not sure if was to clear at all

So I have 2 server
1st server is cloudro ( firewall 80 and 443 to it )
2nd server is a docker that has bit warden running on it

now it is easy to have to have the Clouder server to pass the https over to the docker server on port 443
now the server (2nd server) need to do a ssl key update using letsencrypt BUT can't get the .well-known file
if I recall it need to do this with http ( bbs has the some error too when it try with the server's do not have the folder)

https://letsencrypt.org/how-it-works/ ( if I am reading that right ) need to come in as http to access .well-known folder.

Hope that better

[james]

Hello @nozy

Why are you running a custom Bitwarden on a second server if you could just install @vaultwarden on your Cloudron server?
Also, the second server would only need to serve Bitwarden on http and the Cloudron Proxy app should point to that http://$IP:$PORT.
I still need more details why the second server needs the ssl key if you plan to use the Cloudron Proxy app?

[nebulon]

I see so you probably have deployed bitwarden with some additional reverse proxy which wants to setup SSL/TLS hence tries to get a certificate from letsencrypt. Since Cloudron's proxy app already handles this part, you just have to disable this in your bitwarden setup and proxy bitwarden directly.

For context, most likely your setup is trying to get a cert via http which won't work as it wont reach it, since Cloudron sits on that already and always forwards to https.