Hey there! We've found the following might help you get unblocked faster:

• 🧵 Next.js + MongoDB Private URL on Railway - Connection Issues During Deployment

• 🧵 Railway Support Ticket: Private Networking Not Resolving

• 🧵 Monorepo Deployment Issues

If you find the answer from one of these, please let us know by solving the thread!

Can you screenshot the private networking portion of Frank?

For sure! Here you go @samgordon:

Can you share the entire deployment logs as well? Private networking looks correct.

Yea I've been through all the obvious stuff and it works fine with the public URL.

Here are the deploy logs for the cron service:

[Region: us-east4]

=========================

Using Detected Dockerfile

=========================

context: 46sv-QsrM

internal

load build definition from Dockerfile

0ms

internal

load metadata for docker.io/library/alpine:latest

132ms

auth

library/alpine:pull token for registry-1.docker.io

0ms

internal

load .dockerignore

0ms

1

FROM docker.io/library/alpine:latest@sha256:4b7ce07002c69e8f3d704a9c5d6fd3053be500b7f1c69fc0d80990c2ad8dd412 cached

5ms

2

RUN apk add --no-cache curl

1s

OK: 12 MiB in 25 packages

importing to docker

48ms

auth

sharing credentials for production-us-east4-eqdc4a.railway-registry.com

0ms

Build time: 9.46 seconds

Here are the logs for frank:
Starting Container

Prisma schema loaded from prisma/schema.prisma

Datasource "db": PostgreSQL database "railway", schema "public" at "pgvector.railway.internal:5432"

27 migrations found in prisma/migrations

No pending migrations to apply.

npm notice

npm notice New patch version of npm available! 11.6.2 -> 11.6.3

npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.6.3

npm notice To update run: npm install -g npm@11.6.3

npm notice

WARNING: Found migrations in database but not in code:

- 20251115212417_add_ai_provider_name_and_is_global

- 20251115212522_add_selected_embedding_model_to_frank_settings

- 20251115212719_add_primary_to_calendars

- 20251115213204_add_archived_at_to_frank_conversations

- 20251115214204_add_global_search_settings

- 20251115214427_add_frank_message_observability_fields

- 20251116130232_add_agent_run_step_observability_fields

- 20251117021711_add_task_archived_and_templates

This can cause ordering issues. Consider cleaning up orphaned migrations.

These might be from deleted branches or manual database changes.

All 27 code migrations are properly recorded in the database.

(8 orphaned migrations in DB are not critical but should be reviewed)

> frankapp@1.0.0 start

> next start

▲ Next.js 15.5.6

- Local: http://localhost:3000

- Network: http://10.152.216.114:3000

✓ Starting...

✓ Ready in 395ms

The Cron Job itself is literally just a Dockerfile:

FROM alpine:latest

# Install curl
RUN apk add --no-cache curl

# Add delay for network readiness, then make the request
CMD ["sh", "-c", "sleep 3 && echo \"Calling: $APP_URL/api/cron/calendar-sync\" && curl -X POST $APP_URL/api/cron/calendar-sync -H \"Authorization: Bearer $CRON_SECRET\" -H \"Content-Type: application/json\" && echo \"\nRequest completed with exit code: $?\" || (echo \"\nRequest failed with exit code: $?\" && exit 1)"]

Ha! I figured it out, I had to hard code the port to 3000. For whatever reason the public API automatically uses the right port but the internal port gets set to 80 which the API isn't listening on.