Error response from daemon: driver failed programming external connectivity

#1

So I keep getting this error whenever I try to docker compose up -d:
Error response from daemon: driver failed programming external connectivity on endpoint management-server-1 (2f7aca3fad986f6534c814f1e373a0d666aa92bcb49f3520c752d7748597ed4c): Error starting userland proxy: listen tcp4 [REDACTED IP]:1454: bind: cannot assign requested address

The management-server-1 is not started but the database is started. I already checked my server firewalls and ports and the port is not redundant.

I followed the documentation and here’s my docker-compose.yaml and .env files:
docker-compose.yaml

version: '3.5'

services:
  server:
    image: cortezaproject/corteza:${VERSION}
    restart: always
    env_file: [ .env ]
    depends_on: [ db ]
    ports: [ "[REDACTED IP]:1454:80" ]

  db:
    # PostgreSQL Database
    # See https://hub.docker.com/_/postgres for details
    image: postgres:13
      #    networks: [ internal ]
    restart: always
    healthcheck: { test: ["CMD-SHELL", "pg_isready -U corteza"], interval: 10s, timeout: 5s, retries: 5 }
    volumes:
      - "dbdata:/var/lib/postgresql/data"
    environment:
      # Warning: these are values that are only used on 1st start
      #          if you want to change it later, you need to do that
      #          manually inside db container
      POSTGRES_USER: [REDACTED]
      POSTGRES_PASSWORD: [REDACTED]

volumes:
  dbdata:

.env File


########################################################################################################################
# docker-compose supports environment variable interpolation/substitution in compose configuration file
# (more info: https://docs.docker.com/compose/environment-variables)

########################################################################################################################
# General settings
DOMAIN=[REDACTED IP]:1454
VERSION=2022.9

########################################################################################################################
# Database connection

DB_DSN=dbuser:dbpass@tcp(db:3306)/dbname?collation=utf8mb4_general_ci

########################################################################################################################
# Server settings

# Serve Corteza webapps alongside API
HTTP_WEBAPP_ENABLED=true

# Send action log to container logs as well
# ACTIONLOG_DEBUG=true

# Uncomment for extra debug info if something goes wrong
# LOG_LEVEL=debug

# Use nicer and colorful log instead of JSON
# LOG_DEBUG=true
########################################################################################################################
# Authentication

# Secret to use for JWT token
# Make sure you change it (>30 random characters) if
# you expose your deployment to outside traffic
# AUTH_JWT_SECRET=fNp0zVuGNr8gOs79yDJlIP6OByk7x36zTlYz4cyZyvqQavBbSb

########################################################################################################################
# SMTP (mail sending) settings

# Point this to your local or external SMTP server if you want to send emails.
# In most cases, Corteza can detect that SMTP is disabled and skips over sending emails without an error
#SMTP_HOST=[REDACTED]
#SMTP_USER=[REDACTED]
#SMTP_PASS=[REDACTED]
#SMTP_FROM=[REDACTED]

How do I fix this?
Also removing the IP from docker-compose.yaml from “[REDACTED IP]:1454:80” to “1454:80” would start without errors spouting up in the console, but accessing the webpage will get this:

Corteza server initializing

FAIL Scheduler: stopped
PASS Mail
PASS Corredor