nextcloud bad gateway 502, i screwed up.

Zoki · 3. Dezember 2021

Add a file as attachment.

docker inspect e79b21c94575 > the_file_to_attach

HackitZ · 3. Dezember 2021

here's the out put of docker restart e79b21c94575:

Code

root@MEDIA-SERVER:~# docker restart e79b21c94575                                                                                                                                                                                                                                   
Error response from daemon: Cannot restart container e79b21c94575: driver failed programming external connectivity on endpoint Nextcloud (e3d8ae61f12df24970b9d1acb76083a0584968f0b4c12f3adff0e31ba2f57378): Bind for 0.0.0.0:444 failed: port is already allocated                
root@MEDIA-SERVER:~#

both seem to point to a port conflict issue.

HackitZ · 3. Dezember 2021

here's the inspect out put.

Zoki · 3. Dezember 2021

but now the fix should be easy. You can not have two programs listen to the same port.

Rethink your config.

If you

HackitZ · 3. Dezember 2021

yeah need to figure out what ports i used before.

is it config.php i edit?

sorry for the simple question.

Zoki · 3. Dezember 2021

Check your containers, if one is listening on 443 or it is OMV Web GUI itself.

sudo netstat -tulpen will give you the list of ports listened on and the respective program.

KM0201 · 3. Dezember 2021

Zitat von Zoki

Check your containers, if one is listening on 443 or it is OMV Web GUI itself.

sudo netstat -tulpen will give you the list of ports listened on and the respective program.

You could also

Code

docker ps -a | grep port_number

Code

ken@openmediavault:~$ docker ps -a | grep 444
c110f37ed0ea   ghcr.io/linuxserver/swag:latest          "/init"                   33 hours ago   Up 24 hours             0.0.0.0:81->80/tcp, :::81->80/tcp, 0.0.0.0:444->443/tcp, :::444->443/tcp   swag
ken@openmediavault:~$

HackitZ · 3. Dezember 2021

If i know the port to change where do i make this change? is it in the letsencypt config? if so whats the file called?

Zoki · 3. Dezember 2021

It depends, what program is using the port. If it is one of the docker containers, you have to update the docker container config. How you do it depends, how you configure your containers:

docker-compose: change docker-compose.yml
docker: change the connand line / script you use to start
portainer: update stack or docker definition

HackitZ · 3. Dezember 2021

Seems i used docker compose. so i know i corrupted nextcloud container. when i look at my nexcloud config.php it seems fine. i'm confused why i now have a port conflict issue?

should i be trying to edit a different file other than the config.php. I'm guessing as soon as i figure out the conflict i'll be able to start the nextcloud container.

Zoki · 3. Dezember 2021

Please paste the docker-compose.yml here. Do not change other config files.

Do you know which program is using 443?

HackitZ · 3. Dezember 2021

It's fixed, thanks for all the help.

like i mentioned earlier OMV just works. i mess with it so little i forget the basics.

here's what i did.

Removed the container inside docker.

(this is why you asked what i used)

re-ran docker-compose.yml

Nextcloud fired right up.

Sorry for wasting everyone's time.

but thanks for the help

Soma · 3. Dezember 2021

Zitat von HackitZ

Seems i used docker compose.

You only need to show the docker-compose.yml file that you created and used.

If you don't know where it is, try:

sudo find / -name docker-compose.yml

Might show something like:

Code

pi@tacho:~ $ sudo find / -name docker-compose.yml
/home/pi/nextcloud/docker-compose.yml
/home/pi/pihole/docker-compose.yml

HackitZ · 3. Dezember 2021

This has caused me to realize i probably should run version 6.

at some point we won't be getting updates for version 4.

Would i be better off trying to upgrade or just do a clean install?

Zoki · 3. Dezember 2021

Zitat von HackitZ

This has caused me to realize i probably should run version 6.
at some point we won't be getting updates for version 4.
Would i be better off trying to upgrade or just do a clean install?

If you can easily reproduce the config, do a fresh install, if not, you have to update. But stop at OMV5 until OMV6 is released and all your plugins are ready.

HackitZ · 3. Dezember 2021

so i'm back to the two warnings.

Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.

is this a mac sync issue only?

Zoki · 3. Dezember 2021

It is a nextcloud thing. Check their forums: https://help.nextcloud.com/sea…finger%20nodeinfo%20nginx

Soma · 3. Dezember 2021

Zitat von HackitZ

so i'm back to the two warnings.
Your web server is not properly set up to resolve "/.well-known/webfinger". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/nodeinfo". Further information can be found in the documentation.
is this a mac sync issue only?

Are you running SWAG alongside the Nextcloud?

HackitZ · 3. Dezember 2021

Zitat von Soma

Are you running SWAG alongside the Nextcloud?

No i don't think so. how can i check?

Soma · 3. Dezember 2021

Post the contents of your docker-compose.yml

Hide sensible data

Jetzt mitmachen!