lukasgjetting
Unable to connect to newly migrated MySQL service from outside the Railway network
Hi there! I just migrated a legacy MySQL plugin to a service using the migration tool.
My API service can correctly connect to the database using the internal domain (
database.railway.internal
).
However, I am unable to connect to the MySQL service from my own machine, using the public domain proxy (roundhouse.proxy.rlwy.net:22516
).
I receive the following error:
Seems like there is an issue with the initial handshake, which might be a problem with the proxy?7 replies
Python not available after recent update(?)
Hiya! I've been deploying via Railway for almost a year now - and it's been great!
Starting three days ago, all my builds are failing with the error message
Python is not set from command line or npm configuration
while building node-gyp.
I am deploying JS using yarn
.
Did a recent update to Railway change anything? Is the default image now more lightweight, meaning Python isn't included?
And if so, is there a way to do this while avoiding a custom Dockerfile?
I could try to guess the python location and set it as an environment variable, but that seems very brittle...
Thanks!
---
Project ID: 07fcde41-284c-48e1-83d0-a92b28b116fc
Full error:
25 replies
Unable to connect to a custom MySQL deployment (Dockerfile + volume)
I am currently trying to deploy MySQL via a custom Dockerfile (I need to change
innodb_ft_min_token_size
, which is not possible with the default MySQL deployment).
I am using a simple Dockerfile:
Looking at the build + deploy logs, everything seems to work correctly. However, I cannot connect to the database.
I have connected a default Railway domain. When accessing it via a browser, I get the following error: upstream connect error or disconnect/reset before headers. reset reason: protocol error
.
When connecting to <railwayDomain>:80
via MySQL Workbench, I get the following error: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
.
Trying to connect to port 3306 results in a timeout.
Am I missing anything? Thanks. 🙂13 replies
Changing MySQL system variables (innodb_ft_min_token_size)
Hi! I want to change the
innodb_ft_min_token_size
system variable for improved search.
Here, https://docs.railway.app/databases/mysql#changing-system-variables, it is mentioned that changing system variables is not supported.
1. Is there any alternative solution? I would like to still host the database on Railway. Maybe combining the new docker image deploy with a volume?
2. Are there any plans to support natively changing MySQL system variables like the one I mentioned? And if so, what is the ETA?
Thanks!10 replies
MySQL server seems to be given way more memory than needed
Hi!
About a month ago, I messed up some queries, causing Railway to allocate my database service 10 GB memory.
Now, a while after the problem has been fixed, it seems to still be floating at 5-7 GB - even with very little activity!
Hope that makes sense - thanks
Project ID is 07fcde41-284c-48e1-83d0-a92b28b116fc
6 replies
Additional DNS records on same domain as a Railway application
Hi! I am hosting a landing page on Railway with a custom domain using a CNAME record.
Now, I am also setting up an email client via Namecheap (their PrivateEmail service). To send emails from @mydomain.com, I have to add an MX record and a TXT record (SPF).
However, the DNS spec states that, "if a CNAME record is present, no other data should be present" (https://serverfault.com/questions/834320/adding-both-cname-and-txt-dns-records-for-one-subdomain).
Because of this, my emails fail the SPF check while the CNAME is active.
I have tried removing the CNAME record, which makes the SPF succeed...
This seems like a very common usecase - am I missing something?
Do I somehow not have to set up MX/TXT records on the root domain (host: @) to succeed SPF check while sending emails from [email protected]?
Thanks!
6 replies
Yarn install frequently fails with ENOENT
Hi! My builds fail quite frequently because of an allegedly missing package when running
yarn install
.
The package causing the error seems to change, so I don't think it's because of a specific package.
This happens during the install
phase, so before it reaches any of my code.
Thanks!
Error message:
Project ID: 07fcde41-284c-48e1-83d0-a92b28b116fc
Config:
╔════ Nixpacks v0.10.2 ════════╗
║ setup │ nodejs-16_x, yarn-1_x ║
║────────────────║
║ install │ yarn install --frozen-lockfile ║
║────────────────║
║ build │ yarn build:api ║
║──────────────║
║ start │ yarn run-build:api ║
╚══════════════════════╝3 replies