Is that for IP-based virtual hosts?
And will free subdomain work for this when I go ahead and try to use a DNS to reach my server after I've gotten this to work? Just want to ask this first, just in case.
I can read about how to define a front-facing vhost in the examples and documentation, right?
From: Frank Gingras <thumbs@xxxxxxxxxx>
Sent: Saturday, September 22, 2018 4:07 AM
Subject: Re: [users@httpd] IP address used by Apache reverse proxy?
In a nutshell, you need to:
1) Define a front-facing vhost. You can use DNS and name-based vhosts to reach it
2) Decide what URI path you want to proxy in that vhost
3) If you proxy / (i.e. every request), then you don't need a DocumentRoot in that vhost. Otherwise, you need one
4) You don't need to use DNS to specify the target of your backend server. ProxyPass / http://IP_HERE:PORT/ is perfectly fine.
5) I actually recommend that you do not use DNS to reach the proxied server, initially. Keep things simple first.
Let me just say again, first, that I have a subdomain name I want to use for my app.
Okay. Anyway, when I tried to get to my app just now after starting the Apache httpd as a service, I got an error page in Edge saying that it can't reach the page. I'd like to show you my httpd configuration file again to make
sure if I have the reverse proxy configuration done correctly.
I want to know the IP address so I can use it in my hosts file, since you said I can add an entry to the hosts file mapping that IP address to a given name domain name (or subdomain name in my case). Though I'm not sure if doing
it like that would make the app publicly available from anywhere.
What happens if I set up an IP-based virtual host instead? And how easy or hard would it be to map a domain or subdomain name to that IP address?
Another question: the current file path I have for my virtual host DocumentRoot setting is the one my app's files are in. Should I set it to the htdocs folder instead (if so, how do I tell it that it what files it has to serve behind
a reverse proxy?)?
The IP httpd will use to proxy to your backend isn't typically relevant, unless you want to apply filtering or tracking of some sort.
Can you start over and tell us what problem you're trying to solve, again?
I've already read about networking and DNS to some extent. I'll read about them some more, though.
But I still think I should know how to find the IP address used by the Apache reverse proxy server. Just in case.
Starting another thread to ask the same question is a bit ill-advised. I would still recommend that you get up to speed on networking and DNS basics, first.
Next, you should read the following docs:
How do I find the IP address?
Would it be possible to use that IP address with a subdomain name on a virtual host configuration? I want to use the free subdomain I got from
To unsubscribe, e-mail:
For additional commands, e-mail: