Cannot access AIO Nextcloud behind sophos xg

Dear all,

I have a fresh AIO Docker install on a proxmox VM.
I’ve configured a sophos DNAT Rule to forward Port Https traffice to the nextcloud. The DNS is configured as DDNS @ duckdns. I’ve followed the following post here:

Anyhow, NC is not accessible from outside. Does Docker needs any special rules in the XG Sophos firewall? The actual FW DNAT Rules are created by the DNAT wizard. Before the docker stuff, I had a proxmox lcx container and it worked like charm. what could be else done. Explanations and step by step solutions are welcom instead of Links

Greetings

Haydar

I’ve configured a sophos DNAT Rule to forward Port Https traffice to the nextcloud.

So just 443/tcp for the regular NC interface not AIO itself, correct? I assume you’re only trying to get NC itself not AIO to be reachable from outside?

Anyhow, NC is not accessible from outside.

What precisely happens? What happens if you use your public IP address rather than relying on DNS? etc.

Is everything in the AIO interface everything is green?

e.g. accessed internally:

https://ip.address.of.this.server:8080
https://ip.address.of.this.server:8443

have you updated the trusted sites list…

Hello and thanks for the response:

I did the following steps to installe the AIO Docker incl. NC

  1. Created a new Bookworm VM on Proxmox. Added a an local IP Number and made a DNAT on this IP on Sohpos

  2. Followed the steps in the description: https://nextcloud.com/de/blog/how-to-install-the-nextcloud-all-in-one-on-linux/

  3. Added my DDNS Name of the nextcloud

  4. Here I got error message, that domain name is not reachable on port 443.

  5. BTW How do I add my server to the permited servers in the config file of NC. Every seems to changed a lot, where I would expect the settings files. Where do I have to add the trusted sites list…

And what do you mean exactly with:

So just 443/tcp for the regular NC interface not AIO itself, correct? I assume you’re only trying to get NC itself not AIO to be reachable from outside?

You may want to check out the actual AIO README documentation. It’s more up-to-date and extensive:

It’s pretty much the same and it didn’t help either. The point is, that I’ve installed docker on the linux box as shown under point 2 and 3 of this documentation, but when I even try the IP with https, I canot access nextcloud. What are the correct steps, since this documentation doesn’t help really much. Thanks for your help

BTW: what do you mean exactly with:

So just 443/tcp for the regular NC interface not AIO itself, correct? I assume you’re only trying to get NC itself not AIO to be reachable from outside?

However, this docker stuff doesn’t work on my systems. Must I use “Docker” to use NC, or can I install NC on a old school without using docker?

You can install NC without any Docker, yes. There are at least six ways to deploy it, and that’s not counting some of the third-party ones.

Please see the Admin Manual:

https://docs.nextcloud.com/server/latest/admin_manual/installation/source_installation.html

EDIT: Btw, I apologize if my initial response came off abrupt. Yesterday was a challenging day, and - in hindsight - I was more tried (and grumpy) than I realized at the time.

See step 4 here: GitHub - nextcloud/all-in-one: The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

The URL generally is https://ip.address.of.this.server:8080 internally.

Port 443 is not relevant until you finish the web-based setup in AIO.

Hi, never mind, İ’ve got NC running again over the lxc proxmox conatiner. İ had to update the proxmox container. After the update, NC was downloaded with most recent patch level. So it works out of the box again.

Thanks for all your help. We may mark thos issue as solved

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.