On 8/17/25 1:58 AM, Bret Stern wrote:
Oh I see, you're giving me an example of the text to place in the
configuration file.
I'll search on proxy in the Apache docs, see if I can figure it out.
The subdomain.examplesite.com DNS points to the same address as the
primary website. The server where nextcloud runs
is in the same data center rack on the same lan.
Read this can use alot more traffic, ....than maybe changing my dns,
installing another router with it's own static ip in the rack and have the
link route to the nextcloud server that way.
Any comments?
I'll try to get the reverse proxy working so I understand how to
configure it at least.
Thanks
On 8/16/2025 4:21 PM, Frank Gingras wrote:
On Sat, Aug 16, 2025 at 6:41 PM Bret Stern
<bret_st...@machinemanagement.com> wrote:
Thanks for the suggestion. FYI, my actual domain is not sample.com
<http://sample.com>, I was just using it as an example.
Can you double check that link you included, it's not working and
I want to see the link you refer to.
Best,
Bret
On 8/16/2025 1:22 PM, Daniel Ferradal Márquez wrote:
On 16/8/25 7:04, Bret Stern wrote:
> Have a site www.sample.com <http://www.sample.com> > > From within the
site I
want to a link a subdomain to a nextcloud > server nc.sample.com
<http://nc.sample.com> on the local lan relative to the primary
www > apache > > server. > > > I can add another router with a
static ip, change dns for > nc.sample.com <http://nc.sample.com>
and link to the subdomain using that ip, and serve > nextcloud
that way. > > But I am wondering which (Redirect or Proxy)
methods would work, to > direct traffic to the nc.sample.com
<http://nc.sample.com>. Or if it is good or bad > practice. > >
Thanks for suggestions > > Bret > --
Hello,
To me it seems you want to set up a reverse proxy to yout
nextcloud server. If you set to proxy only specific paths it will
eve make it more secure, for example ProxyPass /nextcloud/
https://subdomain-nexcloud.example.com/nextcloud/
---
Daniel
Help at #httpd in Libera.chat
The target, https://subdomain-nexcloud.example.com/nextcloud/, is an
example here. Modify it to match your DNS.
--
For the record, when you proxy to a SSL/TLS backend with https://xxx you
need to add the additional directive "SSLProxyEngine on" to work.
In any case, when something does not work, just check the error.log or
virtualhost error log from Apache HTTPD server, it will point out what
is going on, as "doesn´t work" is too broad to be useful.
-Daniel
Find help at #httpd in Libera.chat
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org