AIO v3.2.0 Installed - Unable to open Nextcloud after install

🚧 Installation
, ,
1

I just installed the NC-AIO and I’m unable to log in. I get to this page and when I click “open your Nextcloud” it just brings me back to this same page. I don’t know what to check for resolving this. Also I’m trying to add a screenshot, but it keeps erroring out.

2

@aflextwin any joy with this? I have the same issue.

3

I already heard of this problem in the past. The problem back then was that iptables was not running…

4

A screenshot would indeed be very useful.

5

Screenshot_20221223_195316
Screenshot_20221223_1953161157Ă—1061 74.7 KB

This is what I get. I click OK, and then it’s just the spinning circle and nothing loads.

6

I gave up and opted for the VM install. :grimacing:

7

:pensive:
Oh right

8

Interesting! So yeah it should actually open the Nextcloud instance in a new tab. As I said I’ve seen this error before which seemingly was due to iptables not running…

9

What is the output of sudo systemctl status iptables ?

10

Also, can you post the docker run command or docker-compose file here that you used for AIO?

11

sudo docker run
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart always
–publish 80:80
–publish 8080:8080
–publish 8443:8443
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /var/run/docker.sock:/var/run/docker.sock:ro
-e SKIP_DOMAIN_VALIDATION=true
nextcloud/all-in-one:latest

12

I have been testing with Ubuntu and used ufw not iptables

13

This points towards you having configured something incorrectly in your network. Are you running AIO behind a reverse proxy?

14

haproxy on my pfSense box

15

I see. Still iptables is required for docker to work correctly. So what is the output of the command?

16

Unit iptables.service could not be found.
!

17

I see. So we have found the problem. Please follow the reverse proxy documentation to make it work correctly: all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

18

Sorry, my command was wrong. It should be sudo iptables --list. However this is not the problem in your case. Check out my link above!

1 Like
19

So I had trouble with the .toml files because I’m using .yml in my docker configs. I don’t currently know enough about both to convert between them Also I think it said somewhere in there that reverse proxies within your home network WONT work for some reason… But I’m able to do it in a VM no problem

20

I cannot reproduce this, it works without any problem in my home network.