Howto configure Proxy

NethServer Version: 8
Module: sogo nextcloud

We have defined on ISP site A-records
sogo.firma.de … 11.22.33.44 (Public IP)
cloud.firma.de … 11.22.33.44

On Nethserver8 we migrated NS7 to NS8 with sogo.firma.LAN and cloud.firma.LAN . but we don’t know how to configure the proxy Traefik - and we have no access to nextcloud. Looked at NS8-DOKU but it’s too small … Searching for an Howto but not found , I like concrete examples … Reverse proxy is new land

Did you already try to reconfigure Nextcloud by clicking “Save” in the app settings?
Please also check if the hostname and user domain etc are correct in the NC settings…

Usually the proxy is autoconfigured using the app settings for NS8 apps like Nextcloud so there’s no need to change anything.
For example, if you need a reverse proxy for another internal server then you may add a HTTP route here.
You can add domain or path reverse proxies like in NS7.

1 Like

Good morning,

Did you already try to reconfigure Nextcloud by clicking “Save” in the app settings?

Yes, we do so. But If we try https://cloud.firma.lan … Server not found

Is the DNS entry for cloud.firma.lan working?

nslookup cloud.firma.lan.

Are the Nextcloud services running?

runagent -m nextcloud1 systemctl --user status nextcloud nextcloud-app

Are there errors in the logs?

No errors to see

DNS / DHCP is on NS8 with dnsmasq and nslookup cloud.firma.lan shows the IP of NS8 (10.2.2.11)

And after some time … it’s possible to open site cloud.firma.lan from a client in 10.2.2.0 (this is orange LAN = DMZ)
Next step is to open this site from “outside” like cloud.firma.de through the new reverse proxy TREAFIK - but I don’t understand the syntax ?

I assume you use cloud.firma.lan as hostname in the Nextcloud app settings.
This is an internal domain and won’t be resolved correctly from public.

I think the easiest way is to set cloud.firma.de as host name in Nextcloud app settings and change the internal DNS entry to map cloud.firma.de to 10.2.2.11.
This way you don’t need to change a HTTP route. Of course in external DNS cloud.firma.de should point to your public IP and be forwarded to the NS8.

Well, I tried this before and now again …
But in DNSmasq on NS7 were a field for GATEWAY - on NS8 not ??
There is a dns entry for cloud.firma.de >> 10.2.2.11
If I try to open cloud.firma.DE from client at 10.2.2.x get “Bad gateway” …

Which hostname do you use in the Nextcloud app settings, cloud.firma.de or cloud.firma.lan ?

But cloud.firma.lan is still working? I think it’s because the Nextcloud hostname is still set to cloud.firma.lan.
Bad gateway also could mean that NC isn’t started.

Does the client from 10.2.2.x have the right gateway?

You can change it manually if needed:

https://docs.nethserver.org/projects/ns8/en/latest/dnsmasq.html#advanced-configuration

In Nextcloud app settings used cloud.firma.de
Client has a static IP 10.2.2.111 GW 10.2.2.1 DNS 10.2.2.11, 1.1.1.1
The reason is my impatience … and an entry in ReverseProxy.
Now it’s possible to open nextcloud webfrontend and sogo webfrontend from the 10.2.2.-Client :slight_smile:
Next step I try to open from outside - thought I’ve updated all firewall rules…
… and this goes :slight_smile:

1 Like