Could everyone help me ? I don't know where is my setting wrong. I can't open my web mail page. [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711438292-379601-2024-03-26-074634.png] [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711438047-40112-2024-03-26-074553.png] [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711438047-510277-2024-03-26-074718.png] [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711438088-963965-2024-03-25-133640.png]

Leave HTTP_BIND AND HTTPS_BIND empty HTTP_BIND= HTTPS_BIND= Those are for binding to IP addresses

@"[unknown]"#p14299 Thanks for your kind help, but it's not working after motifying. [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711447753-933719-image.png]

@"DocFraggle"#p14299 Thanks for your kind helping but it still can't solve the problem after motifying it.

@"nickydream_"#p14302 Did you restart mailcow after changing the config? ``` docker compose down docker compose up -d ```

Did you check if all the containers are running? Did you check the container logs? Did you check your host's firewall if present? Did you check if any other services are running on the ports mailcow needs?

@"DocFraggle"#p14307 Running. No problem here: [upl-image-preview url=https://community.mailcow.email/assets/files/2024-03-26/1711455895-703794-image.png] But It still can't open the mailcow web

> @"DocFraggle"#p14307 Did you check the container logs? Did you check your host’s firewall if present? Did you check if any other services are running on the ports mailcow needs? ☝️

@"DocFraggle"#p14310 Apart from container logs, I checked firewall, not problem here . And nginx is proxying a web and mailcow, but there are in different ports. I had checked they don't have a Port conflict. Where do I check the container logs? I have checked nginx error log. Also normal.

If you connect to localhost:8080 in your nginx reverseproxy config you have to run mailcow on 8080 HTTP_PORT=8080 Red the docs: https://docs.mailcow.email/post_installation/reverse-proxy/r_p/

HELP!!! nginx proxy mailcow!!

DocFraggle

I would suggest you shut down you current non-working mailcow, completly remove the directory and start over from scratch. I suspect that your mailcow.conf currently contains invalid/invisible characters or something like that which leads to the error message “services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object”

Start over, generate the config and change only the lines

HTTP_BIND=
HTTP_PORT=8080
HTTPS_BIND=
HTTPS_PORT=8443

and maybe the other services ports as you did before.

nickydream_

DocFraggle as well as ports:
- “8443:8443”
- “8080:8080”
in docker-compose.yml ?

I had reinstalled and reset the ports before I asked you. I could try again

DocFraggle

nickydream_ no, don’t touch the docker-compose.yml, it’s using the variables from mailcow.conf

nickydream_

DocFraggle

OK。 Just like before. When I start mailcow , it reports:
root@vmi16215**:/etc/nginx/root/mailcow-dockerized# sudo docker-compose up -d
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object
services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object

I didn’t touch docker-compose.yml .

DocFraggle

nickydream_ How do you edit your mailcow.conf? Do you use an editor? Or vim/nano etc on the console?

nickydream_

DocFraggle
Is there something wrong?

DocFraggle

What’s the output of

file mailcow.conf?

nickydream_

DocFraggle

root@vmi16215**:/etc/nginx/root/mailcow-dockerized# file mailcow.conf
mailcow.conf: ASCII text

DocFraggle

OK, run

egrep "PORT|BIND" mailcow.conf

and paste the output

Ah, try it again WITHOUT sudo! You’re already root and sudo may mess up your environment

nickydream_

DocFraggle

In case you missed my edit, try it again WITHOUT sudo! You’re already root and sudo may mess up your environment

Also please check if you set this to “native” in mailcow.conf:

DOCKER_COMPOSE_VERSION=native

nickydream_

DocFraggle

What do you mean? I didn’t write sudo:

DocFraggle

No, don’t run

sudo docker-compose up -d

BUT

docker-compose up -d

nickydream_

DocFraggle

root@vmi1621588:/etc/nginx/root/mailcow-dockerized# docker-compose up -d
ERROR: The Compose file ‘./docker-compose.yml’ is invalid because:
services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object
services.nginx-mailcow.ports contains an invalid type, it should be a number, or an object

DocFraggle

did you check your DOCKER_COMPOSE_VERSION variable?

nickydream_

DocFraggle

This is the installation record:
Client: Docker Engine - Community
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:17:51 2024
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:17:51 2024
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0

[unknown]

DocFraggle

No…

grep DOCKER_COMPOSE_VERSION mailcow.conf

nickydream_

DocFraggle
root@vmi16215**:/etc/nginx/root/mailcow-dockerized# grep DOCKER_COMPOSE_VERSION mailcow.conf
DOCKER_COMPOSE_VERSION=native

DocFraggle

Maybe you have the old docker-compose installed and that’s messing around… check with

which docker-compose

nickydream_

DocFraggle

This file can’t be read

root@vmi16215**:/etc/nginx/root/mailcow-dockerized# which docker-compose
/usr/local/bin/docker-compose

[unknown]

« Previous Page Next Page »