This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Question about reaching a VM installed on same server.
#1
Question about reaching a VM installed on same server.
This question may or may not belong here, but since I have been forced to reinstall due to a strange unidentifiable bug, now is the time.

My setup and predicament.

I am running CentOS 6.8 (OpenZV kernel) for the host server that is currently running the Sentora installer on it. OpenVZ's kernel is installed and I have one virtual machine to install for running nextcloud (it is actually backed up ready to be dropped back into a new container when I get to it after getting rolling with the native Sentora install.)

My question is simple and I hope ties into my Sentora install. Of course all of the Sentora domains and websites perform as expected on the CentOS 6.8 OpenVz host. What I need to figure out is how to contact the subdomain that contains nextcloud in a CentOS 6.8 container. There is lots of info on the net about OpenVZ containers and Internet connections, but I had no luck with any of it and keep thinking I should be able to adjust one of the virtual host files that I might be able to change from inside Sentora to point the proper subdomain so I can have two way traffic to the nextcloud server.

This may not be a question for Sentora - I am unsure, but I wonder if anyone can guide me as I am pulling my hair out basically due to the fact that there are so many variables and directions one could go though to accomplish this that I have become thoroughly confused!
Thanks in advance.
Everyone makes mistakes, but to truly screw up it takes the root password!
Reply
Thanks given by:
#2
RE: Question about reaching a VM installed on same server.
You can setup a port forwarding if you don't have different ip's for each.

you can use iptables. But if you want to have the aplication in the second container exposed to port 80 you will likely end up setting a proxy forwarding from apache to the mapped port for the container.

Hope you understood me.

M B
No support using PM (Auto adding to IGNORE list!), use the forum. 
How to ask
Freelance AWS Certified Architect & SysOps// DevOps

10$ free to start your VPS
Reply
Thanks given by: worksmarter
#3
RE: Question about reaching a VM installed on same server.
(12-08-2016, 11:40 PM)Me.B Wrote: You can setup a port forwarding if you don't have different ip's for each.

you can use iptables. But if you want to have the aplication in the second container exposed to port 80 you will likely end up setting a proxy forwarding from apache to the mapped port for the container.

Hope you understood me.

M B

Yes I do understand. Thanks so much for giving me direction. There are so many ways I could think of to try I was hoping to have someone help narrow my options. Many thanks M B.
Everyone makes mistakes, but to truly screw up it takes the root password!
Reply
Thanks given by:


Possibly Related Threads…
Thread Author Replies Views Last Post
Server Crash rsthomas 3 6 ,947 05-18-2022, 09:26 AM
Last Post: Nigel
Server Vs. Workstation zHostingSolutions 4 8 ,144 09-14-2021, 06:30 AM
Last Post: sparkrack
Having both HTTP & HTTPS (Port 443 and Port 80) sites on a server dsmarter 14 42 ,812 08-22-2020, 02:49 PM
Last Post: kenzopoker1

Forum Jump:


Users browsing this thread: 1 Guest(s)