503 Service Temporarily Unavailable (online deployment)

🚧 Installation
#1

After initial setup of the online deployment. I am unable to access the platform. My error message is " 503 Service Temporarily Unavailable" ,

The error logs from the server are:

 {"level":"warn","ts":1694255631.5061474,"logger":"store","msg":"could not connect to the database","error":"dial tcp 172.20.0.2:5432: connect: connection refused","try":1,"delay":10}

I am a newbie, so be gentle. Looking forward to your assistance.

#2

IMPORTANT remove any sensitive information from anything you decide to share. You can also share it with me in private messages if you feel more comfortable (but still remove any sensitive information).

Looks like something is off with the database. Can you share your .env and docker-compose.yaml files?

#3

Hi,
I have the same problem.

This is my .env and docker-compose.yaml file:

.env

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

########################################################################################################################
# General settings
DOMAIN=your-demo.example.tld
VERSION=2023.3

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

DB_DSN=postgres://corteza:corteza@db:5432/corteza?sslmode=disable

########################################################################################################################
# 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=this-is-only-for-demo-purpose--make-sure-you-change-it-for-production

########################################################################################################################
# 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=smtp-server.example.tld:587
#SMTP_USER=postmaster@smtp-server.example.tld
#SMTP_PASS=this-is-your-smtp-password
#SMTP_FROM='"Demo" <info@your-demo.example.tld>'

docker-compose.yaml

version: '3.5'

services:
  server:
    image: cortezaproject/corteza:${VERSION}
    networks: [ proxy, internal ]
    restart: always
    env_file: [ .env ]
    depends_on: [ db ]
    volumes: [ "./data/server:/data" ]
    environment:
      # VIRTUAL_HOST helps NginX proxy route traffic for specific virtual host to
      # this container
      # This value is also picked up by initial boot auto-configuration procedure
      # If this is changed, make sure you change settings accordingly
      VIRTUAL_HOST: ${DOMAIN}
      # This is needed only if you are using NginX Lets-Encrypt companion
      # (see docs.cortezaproject.org for details)
      LETSENCRYPT_HOST: ${DOMAIN}

  db:
    # PostgreSQL Database
    # See https://hub.docker.com/_/postgres for details
    # Support for postgres 13, 14 and 15 is available in the latest version of Corteza
    image: postgres:15
    networks: [ internal ]
    restart: always
    healthcheck: { test: ["CMD-SHELL", "pg_isready -U corteza"], interval: 10s, timeout: 5s, retries: 5 }
    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:     corteza
      POSTGRES_PASSWORD: corteza

networks:
  internal: {}
  proxy: { external: true }
#4

My guess would be that you need to change your DOMAIN to whatever you have.
Also worth checking logs for both the server and your reverse proxy

#5

I just wanted to add some information in case anyone else had this issue.

I was running into the same issue setting up a production online deployment. I’m also fairly new to docker.

Looking at the logs, I noticed in the timestamps, that the database wasn’t ready for connections until after the server had attempted, and failed, to connect. There’s also a “hint” in the error that indicated that a delay might be needed, but I wasn’t really sure how to implement:

"try":1,"delay":10

I was able to solve this issue by adding a condition to the database dependency for the server, modifying the “services - server” section of the corteza docker-compose.yaml file like :

depends_on:
      db:
        condition: service_healthy

(I had to remove the [brackets] to pass the syntax check, but that’s probably because I don’t know what I’m doing. :rofl: )

After making this change, the server was able to start and ran through a database schema upgrade.

I was still getting the 503 error, but I’m guessing maybe something didn’t get configured correctly at the beginning since the server wasn’t starting. I started the whole process over again, with the “depends on condition” and things worked properly.

I’m guessing different hosts execute things at different speeds, so that may be why this issue doesn’t impact everyone.