obi 🍍 @obi@qoto.org

@tindall@cybre.space I only install Ubuntu in LTS releases, so it really is exciting times for me

@freemo Didn't realize you were a ham.

I'm KD2QAN lol

@hrisskar truth

I used to like '90s music until my kids just started singing Barbie Girl from Aqua.

@shebang Awesome! Thanks again.

@freemo I assumed it would be easy in docker, but I didn't feel like learning another setup ha. Maybe I should have :(

@shebang Thanks! At least i know it will work lol

@freemo Thanks. Will give it a whirl. Appreciate the help.

@freemo I'm guessing I should be using something with Docker in one VM and create containers and direct traffic, but I have no idea, never dealt with more that one service at once before coming to my IP.

@freemo Yeah, sorry, probably not explaining it well.

I have 2 seperate VMs running ubuntu server on a spare machine in my closet. one with local address ending in .101 running nextcloud, the other running jitsi ending in .190. I have two custom domains pointing at my ip. I have my port forwarding setup for port 80 and 443 to go to .101 for nextcloud. I finally just found the setting to change Jitsi port under an /etc file. I changed that port from 80 to 81, and port forwarded 81 to machine ending in .190.

I guess my only thing i am trying to figure out, is if i can have one domain redirect to my nextcloud, and the other to my Jitsi in the configuration I have it.

@freemo jitsi is the only app running in that vm

@freemo I'm gonna have to dig into these jitsu settings on how to change ports. Its not obvious how. Thanks for the help. I expected I couldn't, but vague people in forums said that they could

@freemo I have 2 VMs, one running nextcloud, another running Jitsi. Both custom DNS pointing to my Ip. Accessing outside network always goes to Nextcloud. I've never dealt with outside access pointing to the same ip and same ports for 2 different services. Not sure how to tell dns how to get to jitsi vm/ip.

@solar@koyu.space Get (back) to Debian, then you can stop :)

@freemo Maybe that's my problem, I set up the VM as a bridged adapter, not a NAT

@freemo The more I try and evaluate this, the more confused I get. Looking at too many sets of data points, some contradictory, some with many more variables, some with what you told me, some showing numbers that says we are overreacting. My head hurts. Too many variables for me today. This topic has fatigued me today :( .

Side question - do you have an tips, or links to an article that may help me with port forwarding? I've done a lot of port forwarding in the past, but just installed a 2nd VM on my home server for Jitsi, and my router either isn't catching it, or i am doing something wrong. Works on local ip, but dns i set to route to public ip, then forward to jitsi vm ip isn't working, goes to an error screen for my nextcloud :(

@freemo thanks. I'm not ideologically, nor emotionally invested in this issue at all. As with most things, just trying to come to the underlying truth.

@freemo I will definitely sit down and reevaluate the numbers with your data. My apologies, as I am trying to look at this while watch my three crazy kids. Thanks for the info. I reserve the right to respond later :p