Scope of cloud flare

This report is to consult the following scenario:

I have two servers identified as srvA (IP: xxxx) and server srvB (IP: yyyy), are servers exactly the same in terms of services, each server has serviceA, serviceB, serviceC, serviceD that are configured by ngixn where you have for each service a reverse proxy to point port 80 out, that is:

serviceA: localport (x1) -> service-domainA

serviceB: localport (x2) -> service-domainB

serviceC: localport (x3) -> service-domainC

serviceD: localport (x4) -> service-domainD

For example, access to server service srvA or srvB is required, it would be indicated by service-domainD, and NGINX detects which service should send that request, however, this scenario is possible in cloud Flare considering that we only have two servers?

ESPAÑOL

Este reporte es para consultar el siguiente escenario:

Tengo dos servidores identificados como srvA(IP:x.x.x.x) y el servidor srvB(IP:y.y.y.y), son servidores exactamente igual en cuanto a servicios, cada servidor tiene servicioA, servicioB, servicioC, servicioD que estan configurados por ngixn donde se tiene por cada servicio un proxy reverso para que apunten de salida el puerto 80, es decir:

servicioA:localport(x1) -> Dominio-servicioA

servicioB:localport(x2) -> Dominio-servicioB

servicioC:localport(x3) -> Dominio-servicioC

servicioD:localport(x4) -> Dominio-servicioD

Por ejemplo, se requiere acceso al servicioD del servidor srvA o srvB, se indicaría por url Dominio-servicioD y el NGINX detecta a cual servicio debe enviar esa peticion, ahora bien, este escenario es posible en cloud Flare teniendo en cuenta que solo tenemos dos servidores?

I’ve read through this three times and don’t see how srvA and srvB are related. Do you want to load balance them?

Are you having a problem with using Cloudflare on non-standard ports?

This topic was automatically closed after 14 days. New replies are no longer allowed.

This report is to consult the following scenario:

I have two servers identified as srvA (IP: xxxx) and server srvB (IP: yyyy), it is required to make a load balancing, they are servers exactly the same in terms of services, each server has serviceA, serviceB, serviceC, serviceD that are configured by ngixn where you have a reverse proxy for each service so that port 80 is output, that is,:

serviceA: localport (x1) -> service-domainA

serviceB: localport (x2) -> service-domainB

serviceC: localport (x3) -> service-domainC

serviceD: localport (x4) -> service-domainD

For example, access to server service srvA or srvB is required, it would be indicated by service-domainD, and NGINX detects which service should send that request, however, this scenario is possible in cloud Flare considering that we only have two servers?

ESPAÑOL

Este reporte es para consultar el siguiente escenario:

Tengo dos servidores identificados como srvA(IP:x.x.x.x) y el servidor srvB(IP:y.y.y.y), se requiere hacer una balanceo de carga, son servidores exactamente igual en cuanto a servicios, cada servidor tiene servicioA, servicioB, servicioC, servicioD que estan configurados por ngixn donde se tiene por cada servicio un proxy reverso para que apunten de salida el puerto 80, es decir:

servicioA:localport(x1) -> Dominio-servicioA

servicioB:localport(x2) -> Dominio-servicioB

servicioC:localport(x3) -> Dominio-servicioC

servicioD:localport(x4) -> Dominio-servicioD

Por ejemplo, se requiere acceso al servicioD del servidor srvA o srvB, se indicaría por url Dominio-servicioD y el NGINX detecta a cual servicio debe enviar esa peticion, ahora bien, este escenario es posible en cloud Flare teniendo en cuenta que solo tenemos dos servidores?

is to do load balancing

This topic was automatically closed after 13 days. New replies are no longer allowed.