carrier plugins not being loaded while deploying & no active carrier connection found #852
Replies: 2 comments 5 replies
-
|
comprehensive api log: karrio.api | Applying events.0003_auto_20220303_1210... OK |
Beta Was this translation helpful? Give feedback.
-
|
Hi @zaryabanwar , There are a couple of issues to unpack here: Plugins not being loaded while deploying
You will notice in the image that I copied over 2 plugins (one stable and the other one with issues). The logs will show you if the plugins failed to load and the error associated. no active carrier connection foundThis generally appears in a couple of scenarios:
To help you with this, you will have to share more about your setup:
I have also updated the API documentation to provide guidance regarding plugin loading and test vs live mode https://www.karrio.io/docs/developing/dashboard-guide |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Can anyone help resolve these issues?
I have deployed karrio on digital ocean droplet with the details below. But still in logs I see the following errors:
karrio.api | 22 objects could not be automatically imported:
karrio.api |
karrio.api | karrio.server.providers.models.carrier.usps_internationalConnection
karrio.api | karrio.server.providers.models.carrier.uspsConnection
karrio.api | karrio.server.providers.models.carrier.upsConnection
karrio.api | karrio.server.providers.models.carrier.sendleConnection
karrio.api | karrio.server.providers.models.carrier.sekoConnection
karrio.api | karrio.server.providers.models.carrier.sapientConnection
karrio.api | karrio.server.providers.models.carrier.purolatorConnection
karrio.api | karrio.server.providers.models.carrier.laposteConnection
karrio.api | karrio.server.providers.models.carrier.genericConnection
karrio.api | karrio.server.providers.models.carrier.freightcomConnection
karrio.api | karrio.server.providers.models.carrier.fedexConnection
karrio.api | karrio.server.providers.models.carrier.eshipperConnection
karrio.api | karrio.server.providers.models.carrier.easyshipConnection
karrio.api | karrio.server.providers.models.carrier.easypostConnection
karrio.api | karrio.server.providers.models.carrier.dpdConnection
karrio.api | karrio.server.providers.models.carrier.dhl_universalConnection
karrio.api | karrio.server.providers.models.carrier.dhl_polandConnection
karrio.api | karrio.server.providers.models.carrier.dhl_parcel_deConnection
karrio.api | karrio.server.providers.models.carrier.dhl_expressConnection
karrio.api | karrio.server.providers.models.carrier.chronopostConnection
karrio.api | karrio.server.providers.models.carrier.canadapostConnection
karrio.api | karrio.server.providers.models.carrier.australiapostConnection
And when I go to the dashboard to create a shipping label in test mode I am able to add carriers and they are marked Active and test_mode is enabled from dashboard but when I add shipper and recipient details I get the following error:
{
"errors": [
{
"code": "not_found",
"message": "No active carrier connection found to process the request"
}
]
}
.env
USE_HTTPS:true
SECRET_KEY=------=
JWT_SECRET=------=
OIDC_RSA_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----"
DATABASE_HOST=----
DATABASE_NAME=----
DATABASE_PORT=5432
DATABASE_USERNAME=------
DATABASE_PASSWORD=-------
DATABASE_ENGINE=postgresql_psycopg2
REDIS_HOST=redis
REDIS_PORT=6379
KARRIO_TAG=2025.5rc19
KARRIO_HTTP_PORT=5002
DASHBOARD_PORT=3002
DOMAIN=example.com
DASHBOARD_URL=https://app.example.com
KARRIO_PUBLIC_URL=https://api.example.com
KARRIO_URL=https://api.example.com
NEXT_PUBLIC_API_URL=https://api.example.com
NEXT_PUBLIC_DASHBOARD_URL=https://app.example.com
NEXT_PUBLIC_KARRIO_PUBLIC_URL=https://api.example.com
NEXT_PUBLIC_KARRIO_API_URL=https://api.example.com
NEXTAUTH_URL=https://app.example.com
ALLOWED_HOSTS=example.com,app.example.com,example.com,localhost,127.0.0.1,api,app
CORS_ALLOWED_ORIGINS=https://app.example.com,http://localhost:3002,https://api.example.com,http://localhost:5002
CSRF_TRUSTED_ORIGINS=https://app.example.com,https://api.example.com
NEXTAUTH_SECRET=${JWT_SECRET}
KARRIO_AUTH_STRATEGY=session
ENABLE_ALL_PLUGINS_BY_DEFAULT=true
ENABLE_CONSTANCE=true
#JWT_ACCESS_EXPIRY=30
ALLOW_SIGNUP=false
ALLOW_ADMIN_APPROVED_SIGNUP=false
PERSIST_SDK_TRACING=true
EMAIL_PORT=465
EMAIL_USE_TLS=false
EMAIL_USE_SSL=true
EMAIL_HOST=example.com
EMAIL_HOST_USER=no-reply@example.com
EMAIL_HOST_PASSWORD="-------"
DEFAULT_FROM_EMAIL=no-reply@example.com
docker-compose.yml
services:
api:
container_name: karrio.api
image: karrio.docker.scarf.sh/karrio/server:$KARRIO_TAG
restart: unless-stopped
ports:
- 5002:5002
depends_on:
- db
- redis
environment:
USE_HTTPS: "True"
DEBUG_MODE: "False"
DETACHED_WORKER: "True"
SECRET_KEY: ${SECRET_KEY}
REDIS_PORT: ${REDIS_PORT:-6379}
REDIS_HOST: ${REDIS_HOST:-redis}
DATABASE_HOST: ${DATABASE_HOST:-db}
DATABASE_NAME: ${DATABASE_NAME:-db}
DATABASE_PORT: ${DATABASE_PORT:-5432}
DATABASE_ENGINE: ${DATABASE_ENGINE:-postgresql_psycopg2}
DATABASE_USERNAME: ${DATABASE_USERNAME:-postgres}
DATABASE_PASSWORD: ${DATABASE_PASSWORD:-postgres}
ENABLE_ALL_PLUGINS_BY_DEFAULT: "True"
ALLOWED_HOSTS: ${ALLOWED_HOSTS}
CORS_ALLOWED_ORIGINS: ${CORS_ALLOWED_ORIGINS}
worker:
container_name: karrio.worker
image: karrio.docker.scarf.sh/karrio/server:$KARRIO_TAG
restart: unless-stopped
command: "/bin/bash ./worker"
depends_on:
- db
- redis
- api
environment:
DEBUG_MODE: "False"
REDIS_HOST: ${REDIS_HOST:-redis}
REDIS_PORT: ${REDIS_PORT:-6379}
DATABASE_HOST: ${DATABASE_HOST:-db}
DATABASE_PORT: ${DATABASE_PORT:-5432}
DATABASE_NAME: ${DATABASE_NAME:-db}
DATABASE_ENGINE: ${DATABASE_ENGINE:-postgresql_psycopg2}
DATABASE_USERNAME: ${DATABASE_USERNAME:-postgres}
DATABASE_PASSWORD: ${DATABASE_PASSWORD:-postgres}
ENABLE_ALL_PLUGINS_BY_DEFAULT: "True"
dashboard:
container_name: karrio.dashboard
image: karrio.docker.scarf.sh/karrio/dashboard:$KARRIO_TAG
ports:
- ${DASHBOARD_PORT:-3002}:${DASHBOARD_PORT:-3002}/tcp
depends_on:
api
environment:
AUTH_TRUST_HOST: "True"
NEXTAUTH_SECRET: ${JWT_SECRET}
DASHBOARD_PORT: ${DASHBOARD_PORT:-3002}
NEXT_PUBLIC_DASHBOARD_URL: ${DASHBOARD_URL}
NEXT_PUBLIC_KARRIO_PUBLIC_URL: ${KARRIO_PUBLIC_URL}
KARRIO_URL: ${KARRIO_URL}
NEXT_PUBLIC_API_URL: ${NEXT_PUBLIC_API_URL}
DASHBOARD_URL: ${DASHBOARD_URL}
KARRIO_PUBLIC_URL: ${KARRIO_PUBLIC_URL}
NEXTAUTH_URL: ${NEXTAUTH_URL}
NEXT_PUBLIC_KARRIO_API_URL: ${NEXT_PUBLIC_KARRIO_API_URL}
caddy:
container_name: karrio.caddy
image: caddy:2.6.2
restart: unless-stopped
ports:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile
- karrio-static:/var/www/karrio/static
- caddy-data:/data
depends_on:
- api
- dashboard
db:
container_name: karrio.db
image: postgres
restart: unless-stopped
environment:
POSTGRES_DB: ${DATABASE_NAME:-db}
POSTGRES_USER: ${DATABASE_USERNAME:-postgres}
POSTGRES_PASSWORD: ${DATABASE_PASSWORD:-postgres}
PGDATA: /var/lib/postgresql/data/karrio
volumes:
- postgres-data:/var/lib/postgresql/data
redis:
container_name: karrio.redis
image: redis
restart: unless-stopped
volumes:
- redis-data:/data
volumes:
karrio-static:
postgres-data:
redis-data:
caddy-data:
Caddyfile
{
email info@example.com
http_port 80
https_port 443
}
api.example.net {
reverse_proxy http://api:5002
}
app.example.net {
reverse_proxy http://dashboard:3002
}
Beta Was this translation helpful? Give feedback.
All reactions