Container failed to start postgres
elefanteartificial
PROOP

9 months ago

After growing mount volume I am bot being able to connect.

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

Container failed to start

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

This image does not have a "8256eb7d-d21d-4f32-89ab-d1ba06ff54da" tag.

Closed

3 Replies

9 months ago

Hello,

This appears to be a transient issue with GitHub's container registry that occurred at an unfortunate time. Unfortunately, issues with external services are outside of our control.

I can see that your latest deployment is now online and working without issues, so I'm marking this as resolved.

Best regards,

Brody


Status changed to Awaiting User Response Railway 9 months ago


Status changed to Solved brody 9 months ago


brody

Hello, This appears to be a transient issue with GitHub's container registry that occurred at an unfortunate time. Unfortunately, issues with external services are outside of our control. I can see that your latest deployment is now online and working without issues, so I'm marking this as resolved. Best regards, Brody

elefanteartificial
PROOP

9 months ago

Im still getting error in connection of n8n with the postgres server.

ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/ for more information.

at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:187:13)

at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:398:22)

at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:671:20)

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:724:32

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:704:5 {

code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',

help: 'https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/'

}

(node:1) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.

(Use node --trace-deprecation ... to show where the warning was created)

ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/ for more information.

at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:187:13)

at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:398:22)

at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:671:20)

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:724:32

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:704:5 {

code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',

help: 'https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/'

}

ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/ for more information.

at Object.xForwardedForHeader (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:187:13)

at Object.wrappedValidations. [as xForwardedForHeader] (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:398:22)

at Object.keyGenerator (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:671:20)

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:724:32

at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/express-rate-limit@7.5.0_express@5.1.0/node_modules/express-rate-limit/dist/index.cjs:704:5 {

code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',

help: 'https://express-rate-limit.github.io/ERR%5FERL%5FUNEXPECTED%5FX%5FFORWARDED%5FFOR/'

}


Status changed to Awaiting Railway Response Railway 9 months ago


9 months ago

That would be an unrelated issue. For that, please open a new thread.


Status changed to Awaiting User Response Railway 9 months ago


Status changed to Closed brody 9 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...