Swag Nextcloud Docker reach internal IP

I have not seen the videos. But here you have a guide to configure the same and a thread with all the answers.

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

That video is over three years old. There will probably be some outdated things.

By the way. OMV4 is EOL. You should consider upgrading to OMV5. Or even OMV6 RC if the plugins you need are already ported. You can see the progress here.

omv-extras plugins - porting progress to OMV 6.x

You really need to move to OMV5, or even 6. This Nextcloud how-to is the going method currently: [How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Posting to watch the thread.

Will reply when I manage some free time

I think we ran the op away. We didn’t tell him what he wanted to hear.

Have not watched the vidoe, but you can try to add two seperat reverse-proxy configigurations pointing to nextcloud.

If yoiu have a local DNS, you can easily add a name insead of choosing a different port.

Quote from Zoki

Have not watched the vidoe, but you can try to add two seperat reverse-proxy configigurations pointing to nextcloud.

If yoiu have a local DNS, you can easily add a name insead of choosing a different port.

The issue is on the rewrite of the config.php that belongs to Nextcloud.

So the only option is to have the internal DNS overrider the public DNS-Name and point it to the internal IP.

Quote from Skullchuck

So after contemplating I believe there's no way to manage this in my current setup. The issue is that calling the new external port (450) directly leads me to a default page of Swag. I suppose Swag behaves this way to prevent bypassing the proxy (blocking anything that doesn't come via DuckDNS), so it's a security feature that I definitely don't want to switch off.

Until upgrading one day (or until someone comes up with an awesome solution I will live with it.

I solved it by installing a DNS server on my router. That way I access Nextcloud from LAN with the domain.

Quote from Skullchuck

Hi all,

I configured my Nextcloud docker container with Swag and DuckDNS following these Techno Dad Life videos:

Video 1:

Video 2:

Everything is set up and working fine when I connect via the public URL. However, after setting up Nextcloud in the local network only (video 1), I was able to reach Nextcloud on its local IP (192.168.0.101:444). After installing Swag and DuckDNS (video 2), the local IP will give me ERR_CONNECTION_REFUSED.

The issue is that now whenever I upload something from my local PC, it is apparently routed through the internet, which is slow and unnecessary.

Does anybody know if it is possible to make local IP and public URL working at the same time (and how to configure this)? Or any other way to prevent the local traffic from being routed through the internet?

Thank you in advance!

Cheers

Display More

Very easy...

You need a port for OMV in your docker-compose/stack/whatever you're using in OMV... If you follow below, Nextcloud will be available by subdomain (nextcloud.yoursubdomain.duckdns.org) or by ip (https://ip:450)

RE: Nextcloud Bad Gateway

Near the end where I put the "this is optional" step to comment out port 450... just don't do that, and you'll have unsecured local access and secured remote access. (but you do need to consider upgrading.. OMV 4 has been EOL for a while)

Quote from Skullchuck

Unfortunately this is not possible with my router

If you can't do it on your router you can do it by configuring a DNS server in OMV.

Quote from Skullchuck

And even if – I assume I would just see the SWAG default page again (same as when calling 192.168.0.101:450 directly).

You would see the service because it would enter through Swag on port 443.

it's been ages since I used that plugin

444:443 needs to be in the letdencrypt container (that looks like the nextcloud section). 450:443 needs to be in the nextcloud portion