On 2/5/2024 14:19:24, joe a wrote:
On 2/5/2024 13:24:22, Frank Gingras wrote:On Mon, Feb 5, 2024 at 1:20 PM joe a <joea-lists@xxxxxxxxxxxxxxx <mailto:joea-lists@xxxxxxxxxxxxxxx>> wrote:On 2/5/2024 11:58:55, Frank Gingras wrote: > > > On Mon, Feb 5, 2024 at 11:55 AM joe a <joea-lists@xxxxxxxxxxxxxxx <mailto:joea-lists@xxxxxxxxxxxxxxx> > <mailto:joea-lists@xxxxxxxxxxxxxxx <mailto:joea-lists@xxxxxxxxxxxxxxx>>> wrote: > > In a case where there is only one available incoming IP, is there a > way, > within apache, to host different domains, each on its own internal > server, without requiring the external "calling browser" being any the > wiser? That is, without requiring the browser to "ask again" in a > different manner? > > Want to host a low volume (and low cost) family oriented site (not > apache) without having to resort to additional static IP or move to an > off site "hosted" service. > >> ---------------------------------------------------------------------> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx <mailto:users-unsubscribe@xxxxxxxxxxxxxxxx> > <mailto:users-unsubscribe@xxxxxxxxxxxxxxxx <mailto:users-unsubscribe@xxxxxxxxxxxxxxxx>> > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx <mailto:users-help@xxxxxxxxxxxxxxxx> > <mailto:users-help@xxxxxxxxxxxxxxxx <mailto:users-help@xxxxxxxxxxxxxxxx>> > > > All you need here is name-based vhosts, and reverse proxy to the > internal server when needed. >Since I am not that experienced in apache configuation, I may have somesimple questions. In the modern scheme, should the modules required be specified in httpd.conf or in loadmodule.conf? Does it really matter other than for consistency? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx <mailto:users-unsubscribe@xxxxxxxxxxxxxxxx> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx <mailto:users-help@xxxxxxxxxxxxxxxx>The config file name(s) do not matter, as long as you know what you added and where, and it makes sense for you.Make sure additional config files are included with the Include directive, if you're creating a new file.Woo Hoo! Even I managed it. And, as a bonus, the originally served stuff still works. Well . . . so far.Thanks much.
There are some issues accessing from off premises, that is, when requests are entering via the internet facing router. Like 301 and 400 errors.
Configuration is like this:Internet router-> server-with-apache-redirect-to->server-eith-docker-nginx-reverse-proxy-acme-custom-app. The domain names are the same on each server. Currently believe they must be for certificate generation and use.
The virtual host on apache is configured thusly:
<VirtualHost *:80>
ServerName www.my-domain.com
ServerAlias www.my-domain.org my-domain.com my-domain.org
ProxyPass "/" "http://www.my-domain.com/";
ProxyPassReverse "/" "http://my-domain.com/";
</VirtualHost>
<VirtualHost *:443>
# SSLEngine ON
ServerName www.my-domain.com
ServerAlias www.my-domain.org my-domain.com my-domain.org
ProxyPass "/" "https://www.my-domain.com/";
ProxyPassReverse "/" "https://www.my-domain.com/";
</VirtualHost>
On the apache server the hosts files is used to resolve the host names
to the target server.
Where have I gone wrong? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|