René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG] Error: connect ECONNREFUSED ::1:5432","articleBody":"**Describe the bug**\r\nCheers, \r\n\r\nWhile using the one-click deploy to Railway from the nostream Github page, I'm encountering Error: connect ECONNREFUSED ::1:5432. This seems to indicate that the local network proxy ain't doin' its thing right. \r\n\r\nIs there additional configuration that has to happen for Railway to properly route the DB requests from service to Postgres?\r\n\r\nHere's the error logs starting from `RUN npm run db:migrate`\r\n\r\n#11 [build 6/8] RUN npm run db:migrate\r\n#11 0.857 \u003e nostream@2.1.0 db:migrate\r\n#11 0.857 \u003e knex migrate:latest\r\n#11 1.143 connect ECONNREFUSED ::1:5432\r\n#11 1.143 Error: connect ECONNREFUSED ::1:5432\r\n#11 1.143     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)\r\n#11 ERROR: process \"/bin/sh -c npm run db:migrate\" did not complete successfully: exit code: 1\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n1. Hit that \"Deploy to Railway\" button\r\n2. Keep all default configuration\r\n3. Deploy error. Yikes!\r\n\r\n**Expected behavior**\r\n_Not_ erroring.\r\n","author":{"url":"https://github.com/amunrarara","@type":"Person","name":"amunrarara"},"datePublished":"2024-11-05T02:38:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/379/nostream/issues/379"}