Installation not working on New VPS Server... context cancelled

alexp

Hi,
I am trying to setup a new mailserver on Ubuntu 22.04.4 LTS, VPS Server.
No firewall rules, all packages updated, reverse pointer set.

Following the instructions but I get the following error messages…

Anybody having similar issues? I installed Mailcow a few years back and there were no issues.

Thanks for any advise / help.

Alex

Copying snake-oil certificate... Detecting if your IP is listed on Spamhaus Bad ASN List... Check completed! Your IP is clean root@BWMMail:/opt/mailcow-dockerized# docker compose pull [+] Pulling 11/46 ✘ clamd-mailcow Error context canceled ⠼ ipv6nat-mailcow [⠀⠀⣿⠀] Pulling ⠼ dovecot-mailcow [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling ⠼ nginx-mailcow [⠀⠀⠀⠀⠀⠀⠀⠀] Pulling ⠼ netfilter-mailcow Pulling ⠼ olefy-mailcow [⠀⠀⠀⠀] Pulling ✘ rspamd-mailcow Error context canceled ✘ watchdog-mailcow Error context canceled ✘ mysql-mailcow Error context canceled ⠼ solr-mailcow [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling ✘ dockerapi-mailcow Error context canceled ✘ sogo-mailcow Error context canceled ⠼ ofelia-mailcow [⠀⠀] Pulling ✘ redis-mailcow Error context canceled ✘ memcached-mailcow Error context canceled ⠼ acme-mailcow [⠀⠀⠀⠀⠀⠀⠀] Pulling ⠼ unbound-mailcow [⠀⠀⠀⠀⠀] Pulling ✘ postfix-mailcow Error context canceled ✘ php-fpm-mailcow Error context canceled unknown: <html><body><h1>408 Request Time-out</h1> Your browser didn't send a complete request in time. </body></html>

Client: Docker Engine - Community
Version: 27.0.3
API version: 1.46
Go version: go1.21.11
Git commit: 7d4bcd8
Built: Sat Jun 29 00:02:33 2024
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 27.0.3
API version: 1.46 (minimum version 1.24)
Go version: go1.21.11
Git commit: 662f78c
Built: Sat Jun 29 00:02:33 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.19
GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc:
Version: 1.7.19
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0

docker-buildx-plugin/jammy,now 0.15.1-1_ubuntu.22.04_jammy amd64 [installed]
docker-ce-cli/jammy,now 5:27.0.3-1_ubuntu.22.04_jammy amd64 [installed]
docker-ce-rootless-extras/jammy,now 5:27.0.3-1_ubuntu.22.04_jammy amd64 [installed]
docker-ce/jammy,now 5:27.0.3-1_ubuntu.22.04_jammy amd64 [installed]
docker-compose-plugin/jammy,now 2.28.1-1_ubuntu.22.04_jammy amd64 [installed]

DocFraggle

Did you try to pull again? Maybe it’s a temporary failure

alexp

OK, I found a post somewhere…

ip link set mtu 900 eth0
net.ipv4.ip_forward = 1

This did the trick.

[unknown] I tried multiple times over a period of 2 hrs…

pkernstock

alexp ip link set mtu 900 eth0

This is going to cause a lot of packet fragmentation and kill your network performance, and maybe causing a hell of other issues down the road. I’d strongly advise not to divert from the worldwide standard MTU size of 1500, if not needed.

DocFraggle

pkernstock I’d strongly advise not to divert from the worldwide standard MTU size of 1500

I totally agree! @alexp net.ipv4.ip_forward = 1 should have been set via sysctl while installing Docker iirc… how did you install it?

alexp

pkernstock I was only setting it for docker to download the files. Its not permanent. But thanks for the reply.

[unknown] I used curl -sSL https://get.docker.com/ | CHANNEL=stable sh

I guess thats more on the hosting side. The VPS setup they have.

[unknown]

I used curl -sSL https://get.docker.com/ | CHANNEL=stable sh

I guess thats more on the hosting side. The VPS setup they have.