Specify URL instead of IP:port in network endpoints for applications behind reverse proxy

Mark

8/11/23, 10:54 AM

We are using GCP external HTTPS load balancer, architecture is shown in the diagram below. The primary use of LB is redirecting users to static error site (hosted on Cloud Storage bucket) in case CE instance is down, Traefik crashes on CE, Docker crashes on CE, etc.

We have 4 backend services defined on load balancer:

static-error-page backend bucket
blog-backend-service, gallery-backend-service and shop-backend-service zonal network endpoint groups

Then, we defined host and path rules so that:

https://blog.company.com -> blog-backend-service
https://gallery.company.com -> gallery-backend-service
https://shop.company.com -> shop-backend-service
All unmatched (default) -> static-error-page

Each zonal network endpoint group (blog-backend-service, gallery-backend-service and shop-backend-service) has just 1 endpoint defined: 192.168.171:443 (192.168.171.3 is internal IP of CE instance).

However, since my websites are served behind reverse proxy (Traefik), specifying IP:port combination in network endpoint is useless because they all have the same IP:port. I would like to specify URL instead of IP:port in network endpoint (that way network endpoint would also show correct health status if website is down, it always reports healthy now, even if application is down).

Is it possible to specify URL instead of IP:port in network endpoint? If not, what are my alternatives?

(click on the image to enlarge it)

0 + 0

reverse-proxy

load-balancing

google-compute-engine

google-cloud-platform

Abhijith Chitrapu

8/26/23, 9:21 AM

You can try the option of [Migrating](https://cloud.google.com/traffic-director/tutorials/set-up-internet-neg#migrate-to-internet-neg) from an IP:Port NEG to an FQDN:Port NEG

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Specify URL instead of IP:port in network endpoints for applications behind reverse proxy

TH: ระบุ URL แทน IP:port ในปลายทางเครือข่ายสำหรับแอปพลิเคชันที่อยู่เบื้องหลังพร็อกซีย้อนกลับ

RO: Specificați adresa URL în loc de IP:port în punctele finale de rețea pentru aplicațiile din spatele proxy invers

RU: Укажите URL-адрес вместо IP-порта в конечных точках сети для приложений за обратным прокси-сервером.

VI: Chỉ định URL thay vì IP:port trong các điểm cuối mạng cho các ứng dụng phía sau proxy ngược

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.