Having problems getting off the ground

🚧 Installation
1

I need some help getting my inital setup working.

I have my cloudflare DNS setup to point to my NPM. I have a few other services running through NPM so I think it’s all working ok.

I followed the instructions for NPM. In from HTTP out to the internal IP of NextCloud on port 11000

HTTP - 192.168.1.64 - 11000

Internaly I can connect to NC, but of course I can’t complete it and I can’t connect from the world. So something isn’t right.

My internal NPM address is 192.168.1.63 BTW.

Here is the docker compose file. Any help would be great.

volumes:

nextcloud_aio_mastercontainer:

name: nextcloud_aio_mastercontainer


services:

nextcloud:

image: nextcloud/all-in-one:latest

restart: always

container_name: nextcloud-aio-mastercontainer

volumes:

- nextcloud_aio_mastercontainer:/mnt/docker-aio-config

- /var/run/docker.sock:/var/run/docker.sock:ro

ports:

#- 80:80

- 192.168.1.64:8080:8080

- 192.168.1.64:8443:8443

environment: # Is needed when using any of the options below

- APACHE_PORT=11000

- APACHE_IP_BINDING=192.168.1.63
2

https://www.reddit.com/r/NextCloud/comments/12or055/i_need_some_help_getting_all_setup_please/

3

I brought my post over here because I hoped to get some more varied responses. The trouble shooting didn’t help me.

4

If you are sure that you’ve configured everything correctly then you can simply skip the domain validation and check if you get any further as advised in the last step of the troubleshooting section :wink:

5

That’s the problem. I’m not sure that I have.
When I try to reach it from the world it fails. But internaly it works. I don’t know what I have wrong ether.

6

Unfortunately you didnt provide enough info in order to help you. So I recommend the debugging steps.

7

What other information do you need. I will try to pull what I can.

8

I need to see your npm docker-compose and a screenshot of the npm side where you put in e.g. http://localhost:11000

9

I can do that.
NPM compose file.
services:
app:
image: ‘jc21/nginx-proxy-manager:latest’
container_name: NPM
restart: unless-stopped
ports:
- 192.168.1.63:80:80 # Public HTTP Port
- 192.168.1.63:443:443 # Public HTTPS Port
- 192.168.1.63:81:81 # Admin Web Port
volumes:
- /var/data:/data
- /var/letsencrypt:/etc/letsencrypt

Screenshot 2023-04-19 060138

10

Thanks! So do I understand correctly that npm runs on a server with the ip-address 192.168.1.63 and aio on a different server with ip-address 192.168.1.64?

In that case I would try to set APACHE_IP_BINDING to 0.0.0.0 and disable the Cloudflare proxy feature if it should be active. (Btw point 3 and 7 of all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub)

Do you still get an error then when trying to submit your domain in the aio interface afterwarss? And if yes which one?

11

Thx I’ll try that. Also to be really clear they are 2 separate containers on the same host. I’m not sure if that matters or not.

12

So where do these ip-addresses 192.168.1.64 and 192.168.1.63 come from when the containers are on the same host?

Can you simply try to put the private ip-address of the host into NPM instead of 192.168.1.64? Does it work then (still with apache_ip_binding set to 0.0.0.0)

13

I haven’t been able to try yet. But I will try to try when I get home from work tonight.
These IPs are alias’s on the host. I have several containers that want the same port facing the network. So I created network aliases then bound the containers to different IP’s as needed.

14

That seems to have worked! Thank you for all your time and bearing with my slow learning curve.