8 months ago
Deployment Logs are not downloadable for anything other than the current instance. The Cmd-K dialog will not show "Download Deployment Logs" as an option if the deployment isn't running.
The Log Explorer does not support downloading of logs.
The 'railway logs' command never terminates (presumably because it is running kubectl logs -f which means that the latest log lines are never written when redirected to a file. It also means that the 'railway logs' command hangs.
Looking back through the history of logging complaints, I see people being told to hit Cmd-K to download logs. This is only valid for current instances.
4 Replies
8 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
8 months ago
Hello,
I think this may help you -
https://github.com/brody192/railway-log-downloader
P.S. we don't use k8s.
Best,
Brody
Status changed to Awaiting User Response Railway • 8 months ago
8 months ago
Awesome, thank you. I am also having trouble connecting to my redis instance via the public URL. The REDIS_PUBLIC_URL variable appears to have had the hostname and port stripped. I have tried several different values without success (the operation times out). I also cannot figure out how to find the value for RAILWAY_TCP_PROXY_DOMAIN.
Status changed to Awaiting Railway Response Railway • 8 months ago
8 months ago
Glad I could help!
As for that issue, could I ask you to create a new help thread for that, as it would be a completely different topic than the OP.
Status changed to Awaiting User Response Railway • 8 months ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago