On 2019 Jun 25 18:15:24, you wrote to me:

 ML>> you should have your server proxying https:443 to the TLSPort 444...
 ML>> not to the http post 8081...

 ec> Not necessarily.  OP is probably redirecting 80 -> 443 within nginx,

ok... so we're clear and then bounced to encrypted...

 ec> and then reverse proxying 443 to 8081

but now we're sending encrypted to 8081 that cannot read it?? that doesn't seem
 right...

 ec> so that nginx handles all of the HTTPS (and it's in the clear between
 ec> nginx and the BBS).

ewwwww, what??!? :shudder:

 ML>> are you running NGINX on your BBS machine? is that why you are having
 ML>> to use non-standard ports on the BBS side of the fence??

 ec> I assumed so and it's not an unusual practice.

i know... i used to do the same thing with apache... it just complicates things
 somewhat...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... If you're a zombie you don't want to overschedule.
---
 * Origin:  (1:3634/12.73)