How to? I want to have a URL in my Virtualmin just pass through to another internal physical server inside the network...

I have tried in the past an failed at having Apache and Nginx coexisting on the same physical server.

I want to spin up a PeerTube server which demands Nginx.

If I have a physical server internal to my network that has all the inner workings of the PeerTube instance, how do I make a Virtual Server on my outward-facing Virtualmin managed server that passes through the requests to that internal PeerTube machine?

I assume there are many ways to solve this type of problem but I don't know any of them. I would appreciate being pointed towards any way of solving the problem.

Status: 
Active

Comments

Howdy -- thanks for contacting us!

I'm not quite sure I understand the network design there, but a typical way to do that sort of thing would be to setup some sort of port forwarding.

If the request is destined for a particular IP address, just have all requests forwarded in to your internal server.

If you have additional questions, we may need to hear more about your network setup, and we'll see if we can point you in the right direction.

WNYmathGuy's picture
Submitted by WNYmathGuy on Fri, 10/04/2019 - 09:46 Pro Licensee

I'm not professionally schooled in networking concepts at all. I'm more of a barn-yard, will-fit, make-shift type of networking guy.

As of now, I have not tried in any way to spin-up a PeerTube instance.

I have a residential DHCP connection. My outward-facing server has been assigned a reserved address behind my router and is also denoted as the DMZ. It's that way because I don't know any of the better ways to do things. That machine is the Virtualmin managed server. I have a Nextcloud instance running on one of its virtual servers, but because of how things panned out when I switched from MySQL to MariaDB, the Nextcloud's data is on a different server inside my network. I didn't think that was possible before I guessed my way through things under the stress of things going wrong. I have many happy virtual servers on that Virtualmin managed machine. It's operating with Apache but the PeerTube does not offer a way to get its system running on Apache, only with Nginx. Aside: I tried a BigBlueButton thing over a year ago and gave up also because of it only being developed for Nginx.

Because sometimes computers are still magic to me, I assumed I could have another internal server devoted to a PeerTube instance, and somehow just have my outward-facing server pass through requests for it. Is that a no-go? Or is it a "you can't get there from here" type problem? I'm fine with a RTFM type solution, but I don't know how to find the right FM. :)

Sorry for the late reply, I missed your update.

It's definitely worth taking a look at Unborn's suggestion there.

We often suggest having a dedicated IP on your router for forwarding traffic to internal servers, though you can do it other ways with fancier setups and port forwarding.

Unfortunately, what you're looking for there may be getting a bit outside the scope of Virtualmin support. However, you're very welcome to use the Forums to gain some insight into your networking questions there.

WNYmathGuy's picture
Submitted by WNYmathGuy on Wed, 10/16/2019 - 22:07 Pro Licensee

@unborn I think I'll owe you a holiday gift if that works! It seems so obvious after reading your linked post. I thought I would have to do something where I plugged one router into another router and did other fancy set-up things I don't know anything about.

It might be a while before I get to try it, but I'll post and close after I have success.

unborn's picture
Submitted by unborn on Thu, 10/17/2019 - 16:52 Pro Licensee

@WNYmathGuy

Hi, it will works. If you will need any help to set this up, I can help you with it. Just drop me a call via whatsapp or drop me an message via email or here on forums or irc. I am here almost daily.

Edit: its even possible to use lets enctrypt ssl for proxying your nginx via apache.. (https://intranet-your-public-domain -> http://interanet-domain or IP) of course on your internal server should be http only as self signed ssl will give you just error.. by logic if you trust your internal network, you dont need ssl anyway.. but anything coming to https://intranet-your-public-domain would be encrypted so it safe to use it by this way.. I just forgot to mention this :)

have good day chaps!