Community Archive (Customer) asked a question.
using Kemp as reverse proxy
Hello folks,
Im quite new to Kemp and have an plan in my mind but not sure if this is even possible with Kemp or any other solution.
I have the usecase that i host some webbased services currently for myself.To get it clear, following an overview:-PRTG on port 443-Synology NAS1 on port 5001-Synology NAS2 on port 5201-Plex on port 32400
To connect to my services from the "big bad internet" i use my own domain with the given port eg. home.<mydomain>.com:32400 | 5001 | ... In the future i would like to host for example some additional websites or forums which should be on different second- and/or third level domains but with the same public ip. Is this even possible with Kemp and if yes how? I know that there is a way when everything runs on an Apache where you can set virtual services or sth like that but my problem is that all my services running on different machines with different technologies.
Currently my mind is struggeling on the logical part and im not sure if my toughts are correct: My goal ist, that each service will get its own domain name which will be redirected to the selected port of the real servers which runs at home on my ESX. At my home network, each service needs internal an unique port which is not relevant to the "functionality" of the public access (when its an HTTPS Service i dont need to use port 443 for exampe). Does this make any sense? :P
It should look like:.com" rel="nofollow noreferrer">https://plex.<mydomain>.com.com" rel="nofollow noreferrer">https://prtg.<mydomain>.com.com" rel="nofollow noreferrer">https://synstorage.<mydomain>.com...
Thank you already for the help!GreetingsAlex
Im quite new to Kemp and have an plan in my mind but not sure if this is even possible with Kemp or any other solution.
I have the usecase that i host some webbased services currently for myself.To get it clear, following an overview:-PRTG on port 443-Synology NAS1 on port 5001-Synology NAS2 on port 5201-Plex on port 32400
To connect to my services from the "big bad internet" i use my own domain with the given port eg. home.<mydomain>.com:32400 | 5001 | ... In the future i would like to host for example some additional websites or forums which should be on different second- and/or third level domains but with the same public ip. Is this even possible with Kemp and if yes how? I know that there is a way when everything runs on an Apache where you can set virtual services or sth like that but my problem is that all my services running on different machines with different technologies.
Currently my mind is struggeling on the logical part and im not sure if my toughts are correct: My goal ist, that each service will get its own domain name which will be redirected to the selected port of the real servers which runs at home on my ESX. At my home network, each service needs internal an unique port which is not relevant to the "functionality" of the public access (when its an HTTPS Service i dont need to use port 443 for exampe). Does this make any sense? :P
It should look like:.com" rel="nofollow noreferrer">https://plex.<mydomain>.com.com" rel="nofollow noreferrer">https://prtg.<mydomain>.com.com" rel="nofollow noreferrer">https://synstorage.<mydomain>.com...
Thank you already for the help!GreetingsAlex
From what you are saying the Vertual Service is HTTP(s) with SSL ReEncryption enabled ?
...which means the Traffic from LoadMaster to the Real Servers is being re-encrypted (thus the cert requirements) on NAS.
This is fine but I would check to make sure the same is the case for the Docker Services as it would in this case also need to be HTTP(s) since the same Virtual Service is being used.
Barry
I am trying to achieve exactly what Alex stated in his original post. I successfully set up Kemp, my own domain name (with SSL) as well as all of the necessary rules / real servers. For some reason I am having issues with my Synology nas. I use my Synology nas to run Plex (installed through the Synology package center running on the nas) as well as running other services through docker on the nas (e.g. Hoobs, Portainer, etc.). I got plex to work with https://plex.<mydomain>.com , but for the life of me, I cant seem to get the nas or anything running on docker (on the nas) to work.
For now, I am focusing and isolating the nas connection issue... The domain I set up is https://nas.<mydomain>.com as an example. My nas is on port 5000 for http and 5001 for https. On Kemp, I set up the real server based on the nas local IP with port 5001. The rule I am using is set up to redirect https://nas.<mydomain>.com to the nas local IP/port. This is the same logic used when setting up Plex on Kemp. I am not getting any success getting the nas to work. As a side note, I am able to ping https://nas.<mydomain>.com . This is exactly the same issue with everything else running on docker.
Do you know if there is something I need to allow or set up through Synology on the nas itself to allow this connection? Am I missing something?
I should mention that Plex, my Synology nas, and docker containers all use the same local IP however, they have different ports (e.g. Plex port is 32400, while nas http is 5000 and https is 5001 - docker container ports vary as well). This is what is throwing me off. Is this same IP somehow confusing Kemp or is it something I need to change on the nas?
Thank you in advance.
Regards,
Gor
With Kemp SubVs's and Content Rules it is possible to publish a single end point (Virtual Service) and then break traffic out by hostname or url into 'SubVS's each of which can be used for different applications. Note this isn't redirection but rather content switching of traffic. It also assumes all applications are HTTP/HTTP(s).
Each SubVs may then have completely different Real Servers - ie the different machines
So I think the following is what you need:
https://plex.<mydomain>.com https://prtg.<mydomain>.comhttps://synstorage.<mydomain>.com
all pointing to the same Public IP.
Virtual Service (Public IP)
|- SUBVS1- Content Rule plex.<mydomain>.com - different Real Servers and even ports
|- SUBVS2 - Content Rule prtg.<mydomain>.com - different Real Servers and even ports
|-SUBVS3 - Content Rule synstorage.<mydomain>.com - different Real Servers and even ports
Here is some more info on the Content Rules on LoadMaster:
https://support.kemptechnologies.com/hc/en-us/articles/203125019-content-rules
and also an tool that may be of use:
https://support.kemptechnologies.com/hc/en-us/articles/360056719112-New-Tool-Content-Rule-Builder
Barry