Hi,

I'm new to the forum, hello everyone. I hope my question is in the right section.

I want to pass through all http 80 / 443 requests from one server to another, what would be the simplest set up to do this?

What I have currently is the 'old' webserver ( Compute Engine VPS) using Apache and proxyforwarding to the new servers for multiple vhosts.

I want to basically trash the large VPS and re use the IP as the simplest forwarder and the smallest instance I can.

Please let me know if you need any clarification

After removing the large VPS, through what do you want to pass 80/443 requests?

This is what I understand from your question. A client issues a request to a certain IP address+port. You want to route this request to a certain server, based on criteria that are obscure to me. Currently, a separate server (the large VPS) performs the routing, and you want to get rid of it and do it differently.

If my understanding is correct, tell me the routing criteria. However, if you have a single IP address, something (perhaps a small VPS) must decide where those requests go. You seem to be using Google. Does Google have built-in proxy servers or load balancers?

hi @berndbausch

The process is simply a server migration with many client websites.

Rather than wait for the clients to update their DNS - all the sites have been migrated and so now I have a large server just acting as a proxy using apache proxy forward to send the http/https traffic to the new server.

As Google Compute Engine bill by the minute and the IP is transferable, I just want to build a small ( cheap) Google Compute Engine to effectively pass all traffic to the new ( non Google server) whilst I wait for the clients to change their DNS.


As it is a temporary solution I wanted something simple and easy to build.

My research so far has lead me to
- Load Balancers - Google has these
- Protocol Forwarder - Google has these
- Using IPtables - -j DNAT --to

All look to have some complexities and I haven't personally treid any - so sort of looking for guideance here - is it actually worth the effort - or just wait and bear the costs ( which are not that massive )

Give your clients a cut-off date to update their DNS and stick to it. It's amazing how fast they'll actually respond when they can't reach their stuff.

Thanks, that is probably the best idea