Nextcloud AIO mastercontainer missing

I recently spun up an instance of NextCloud AIO using the AWS AMI. Everything went well, I’m pretty sure I clicked the box to install the 26 version (not 25) along with full text search. I was able to access the AIO interface and complete the setup with no significant issues, even did the initial backup. Now I’m noticing that I can’t access the AIO interface anymore. When I check the containers running on the VM, I see apache, nextcloud, fulltextsearch, redis, postgresql and collabora. I’m not seeing the mastercontainer. Also now the admin interface is reporting version 25. How could it have regressed in version? Also how do I get back the mastercontainer running? An help would be appreciated.

Hi, can you run sudo docker ps -a | grep master ?

seems its there but exited 12 days ago.

Can you post the output of sudo docker inspect nextcloud-aio-mastercontainer here?

Any specific parts? I’m seeing a lot of stuff in this JSON and not sure if there’s stuff in here that shouldn’t be shared publicly.

Yes, please run this: sudo docker inspect nextcloud-aio-mastercontainer --format {{.HostConfig.RestartPolicy}}

{always 0}

Also seeing this earlier in the output;

"State": {
            "Status": "exited",
            "Running": false,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 0,
            "ExitCode": 137,
            "Error": "driver failed programming external connectivity on endpoint nextcloud-aio-mastercontainer (b77ed11934fcecacc59da5dd39144fce3ac97e4ab0fc8b952db03774e9e99be1): Error starting userland proxy: listen tcp4 bind: address already in use",
            "StartedAt": "2023-04-20T22:34:16.635858618Z",
            "FinishedAt": "2023-04-21T04:00:07.456972577Z",
            "Health": {
                "Status": "unhealthy",
                "FailingStreak": 0,
                "Log": [
                        "Start": "2023-04-21T03:57:45.936645917Z",
                        "End": "2023-04-21T03:57:46.196640964Z",
                        "ExitCode": 0,
                        "Output": ""

But shouldn’t the master container run on port 8080?

It depends how you started the mastercontainer.

Can you post the output of sudo netstat -tulpn here?

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0    *               LISTEN      679/sshd: /usr/sbin 
tcp        0      0    *               LISTEN      537/nginx: master p 
tcp        0      0   *               LISTEN      1/init              
tcp        0      0   *               LISTEN      1055/docker-proxy   
tcp        0      0 *               LISTEN      413/systemd-resolve 
tcp6       0      0 :::22                   :::*                    LISTEN      679/sshd: /usr/sbin 
tcp6       0      0 :::80                   :::*                    LISTEN      537/nginx: master p 
tcp6       0      0 :::111                  :::*                    LISTEN      1/init              
tcp6       0      0 :::443                  :::*                    LISTEN      1088/docker-proxy   
udp        0      0 *                           563/chronyd         
udp        0      0 *                           413/systemd-resolve 
udp        0      0  *                           411/systemd-network 
udp        0      0   *                           1/init              
udp6       0      0 ::1:323                 :::*                                563/chronyd         
udp6       0      0 :::111                  :::*                                1/init        

So apparently you installed Nginx in the meantime which needs port 80. That is why the mastercontainer fails to start because it wants port 80 as well.

Strange…I didn’t do that. Only thing I did directly in the VM was run the indexing for the memories app. Not sure how that happened. To resolve I’d uninstall the nginx and just restart the box?

yes, that should work

Thanks, it did. I stopped the nginx and started the old mastercontainer and it came up. Not sure what accounts for the bump back to version 25.0.6 but I think I’ll leave well enough alone for now.