HELP!!! nginx proxy mailcow!!

DocFraggle

Yes, because you put your hostname in there. Normally you can leave it empty, that only matters if you want to bind the ports to a specific IP address on your server

nickydream_

I had tried both. Useless 😥

DocFraggle

So… why do you want to use a reverse proxy in the first place? Do you have other webservers running on the host?

nickydream_

DocFraggle
No. I am a personal web developer. It can save money.
I had singly set mailcow without nginx. Successfully.

[unknown] I just have a server.

DocFraggle

OK, check the nginx container logs:

docker compose logs nginx-mailcow

Maybe you can see something there. curl on your port 8080 should work at least and show the 301 redirect…

nickydream_

The datas are so many. This the lasted one:

DocFraggle

What’s the current output of

curl -v http://127.0.0.1:8080

nickydream_

DocFraggle
Empty:

root@vmi16215**:~# curl -v http://127.0.0.1:8080

Trying 127.0.0.1:8080…
TCP_NODELAY set
Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)

GET / HTTP/1.1
Host: 127.0.0.1:8080
User-Agent: curl/7.68.0
Accept: /

Empty reply from server
Connection #0 to host 127.0.0.1 left intact
curl: (52) Empty reply from server

DocFraggle

I’m out of ideas… you can restart your mailcow once again, and after it started run

docker-compose logs --tail=200 -f nginx-mailcow

in one SSH session and do the curl from another session. You should at least see that in the logs
And you can see the start of the logs of the nginx container, maybe it complains about something there

nickydream_

DocFraggle in one SSH session and do the curl from another session. You should at least see that in the logs

Sorry. What do you mean, sir?

DocFraggle

Open two tabs in your SSH client, tail the logs in one session and do the curl in the other session

nickydream_

DocFraggle
This is testing result:

DocFraggle

Sorry, then I’m out of ideas… looks like the other docker containers can talk to the Nginx container just fine

One last thing: did you change anything in your docker-compose.yml because you keep posting it? If you did, revert it to the default, never change anything there! You can override things in the extra yaml file, but for the reverse proxy to work you don’t need to do this

nickydream_

DocFraggle
No. I never do that. I only motified the port in yml, or mailcow can’t run and report wrong ；

Before:

and mailcow report after sudo docker-compose up -d:

root@vmi1621588:/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

That’s why I motified into “8080:80 8443:443”,after that mailcow could work.

By the way if there’s wrong in DNS? I could see it sometimes and sometimes it’s Page not found:

DocFraggle

No, change it back to the default from git! It complained earlier because you had your FQDN in the HTTP(S)_BIND variables instead of an IP address

Your current config is wiring this way

nickydream_

DocFraggle
SO， then, how to deal with mailcow’s error report?

DocFraggle

What’s your current mailcow.conf config regarding the ports and bind?

nickydream_

DocFraggle
I used ./generate_config.sh to change back yml as well as the mailcow.conf . Now, I only changed mailcow.conf again as
HTTP_BIND=
HTTP_PORT=8080
HTTPS_BIND=
HTTPS_PORT=8443

DocFraggle

nickydream_ yes, that should work now. It should render

8080:8080
8443:8443

into the docker config. The part you edited was wrong before, you had

8080:80
8443:443

which can‘t work

nickydream_

DocFraggle

Where should I motify ? Excuese me?

[unknown]

The problem still exits:

nickydream_

DocFraggle Could you still help me, if you online ? Thanks a lot…

« Previous Page Next Page »