I apologize, but the Dunning-Kruger Effect (https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect) say's I'm too dumb to know how to ask for, _or get help,_ correctly.

So here's where I'm at. I'm doing a thing on my own hardware at home behind DHCP. I use the Ubuntu 16.04 LTS Server operating system and manage it with the Virtualmin interface. I've only known Apache for web serving, so it pains me to learn something new. I have a few existing virtual servers running on my DMZ built with Virtualmin and a bunch of subdomains also built with Virtualmin. I decided to make my own subdomain with Webmin from the servers FQDN to run the BigBlueButton software, but they *ONLY* let you do it via Nginx.

After some false starts installing that program, I gave the port 80 and 443 to Nginx's control and my BigBlueButton works pretty good so far. Red-Herring:=(OAuth trouble with Google and HTML5 is fucked up on Ubuntu) So now, I'm using port 591 for Apache's http traffic and port 4433 to serve Apache's https sites. I've read a lot of blogs and posts about how to do this division of traffic and I almost had it working but the SSL sites known to Apache wouldn't serve correctly. The solution I read about which was supposed to fix that SSL problem made nothing on Apache work. So here's my hope...

I can undo the fiddling I did to my Nginx files. Is there an elegant way to have Nginx push all traffic it doesn't have a /etc/nginx/sites-enabled/* file for to Apache's workload? I just don't speak Nginx worth a shit and it really looks like anti-structured nonsense to me most of the time. It seems like I should put some blocks of code in the default /etc/nginx/nginx.conf file that redirects anything caught by the default server to Apache.

Attached is my last rendition of something in my /etc/nginx/sites-available/ folder with the symbolic link to it in /etc/nginx/sites-enabled/ that didn't work for an existing Apache Virtual Host bearing that file's name.

Oh geez, and I almost forgot that the Webmin/Virtualmin management system uses port 10000, but Virtualmin adds apache records for virtual servers to redirect something like admin.wnymathguy.com to https://wnymathguy.com:10000, so that might be different than whatever solves my problem stated above.