04c15714-b519-4459-ac98-c70c2e91f200

for SMTP to work you'd need to specify specific ports on Railway metal's proxy which you can't do yet, and even if you could odds are other people would've taken those ports by now

So unfortunately, SMTP servers can't be hosted on Railway

not yet anyway, maybe once Railway added custom IPs and the ability to specify a port on TCP

so railway doesn't support outgoing SMTP connections?

yes we do, there is no restrictions on outbound traffic

where can I find logs?

logs for what

console for example or node server/js logs. there is literally nothing in the "logs" feature besides a few 200 http entries

click the deploy logs button

again, nothing there besides a few http logs

screenshot please

GET/, POST/ etc. not really helpful. I'm trying to see why email isnt working, despite setting all the variables and code.

this is all there is

HTTP 3/21/2025 12:20:39 AM 100.64.0.4 GET /manifest.json

HTTP 3/21/2025 12:20:39 AM 100.64.0.4 Returned 304 in 1 ms

HTTP 3/21/2025 12:20:39 AM 100.64.0.3 GET /logo192.png

HTTP 3/21/2025 12:20:39 AM 100.64.0.3 Returned 304 in 2 ms

HTTP 3/21/2025 12:20:42 AM 100.64.0.3 POST /api/request-access

HTTP 3/21/2025 12:20:42 AM 100.64.0.3 Returned 200 in 1 ms

screenshot please

thats what your app is printing

so I cant see console logs?

everything I'm doing (with email functions) is working when I test locally. as soon as I deploy to railway, nothing works, despite 200 messages, but I cant see why

those are console logs

its http logs

that is what is being console logged

none of this shows up

/ In my request-access.js
router.post('/', async (req, res) => {
consoleAlert('EMAIL REQUEST RECEIVED');
console.log('Request body:', req.body);

try {
const { email } = req.body;
console.log(Received request for email: ${email});

// Email sending logic...
const result = await sendEmail(email);
console.log('Email sending result:', result);

// Success response
console.log('==== EMAIL PROCESS COMPLETED SUCCESSFULLY ====');
return res.json({ success: true });

} catch (error) {
console.log('Error sending email:', error.message);
return res.status(500).json({ error: 'Failed to send email' });
}
});

then there is something wrong with your code, unfortunately we wouldn't be able to offer coding assistance here

weird that is shows up locally when I run it. but not on railway

is there any documentation on how logging works on railway?

besides telling me my code sucks

How it Works
Any build or deployment logs emitted to standard output or standard error ( eg. console.log(…)) are captured by Railway to be viewed or searched later.

i have console.log all over my files. shows up fine locally. but not in railway. maybe more than 1 sentence for "how it works" would be helpful.

its as simple as that, you console.log and you will be able to see it in the deploy logs, if you arent theres something wrong with your code, not the platform

its literally in the code. and not showing up. ok

I followed your extensive documentation to make it work and its not. and your response is, its my problem. we dont know how railway works under the hood. you do

I'm sorry but this issue isn't related to the railway platform

maybe provide better docs? examples? possible things that cause problems? there is a reason why mine isnt working and I have no idea hwo to make it work on your platform. like I said, it works perfectly fine locally. I cant debug something that works on my end.

console.log("message"); would be the example, I'm sorry but that's really all there is to it

if you aren't seeing the logs you could be looking at the wrong service

console.log('==== EMAIL PROCESS COMPLETED SUCCESSFULLY ===='); all there is to it

yea thumbs up. thanks. it doesnt show up

I'm sorry you're facing difficulties with your code, but we are only able to offer support for the Railway platform here

we have extensive monitoring for our entire logging infrastructure and it's all green

I'm not having difficulty with my code. please stop saying that

I'm asking for support for this platform and the only response I'm getting is my code sucks

I have a mountain of console logs when I run this on localhost. when I deploy to railway, there is nothing

at this point all aspects of that platform are operating correctly and without issues.

and only you know how it works

Yep and I am confidently saying there are no issues on our side at this moment

I'm not even saying there is an "issue" with railway. I'm clearly coding exactly how your 1 line of documentation is suggesting, and its not working. its working fine on my end. but to you, its just one big mystery

maybe start from the basics? a JavaScript file with only a console log

you mean like this?

node test-smtp-connection.js

!!!!! SMTP CONFIGURATION !!!!!

Host: smtp.hostinger.com
Port: 465
Secure: true
User: noreply@spendspace.io

Pass:

!!!!! STARTING SMTP TESTS !!!!!

Network Interfaces:

- Wi-Fi: 192.168.1.89

!!!!! TESTING TCP CONNECTION !!!!!

Attempting to connect to smtp.hostinger.com:465…

TCP connection successful!

!!!!! TESTING TLS CONNECTION !!!!!

Attempting TLS connection to smtp.hostinger.com:465…
TLS connection authorized!
TLS Protocol: TLSv1.3

Cipher: TLSAES256GCMSHA384

!!!!! TESTING SMTP AUTHENTICATION !!!!!

Verifying SMTP connection…
SMTP Verification Result: true

I'm sorry but I'm not sure the relevance of that to what I just said

those are console logs

I'm going to have to step back here and let the community involve themselves with this thread and they can offer you coding assistance if they so choose

so you have no idea why those console logs show up locally but not in railway? they are all literally console.log()

coding assistance. nice dig

it's funny how neither of you actually tries to debug the issue

I'd love to! thats what logs are for. but I cant see any here

ok lets start from a different angle

what prints those $DATE $IP Returned $CODE?

I would assume it comes from somewhere in your code

// Get network information
try {
const { networkInterfaces } = require('os');
const nets = networkInterfaces();
console.log('Network Interfaces:');
for (const name of Object.keys(nets)) {
for (const net of nets[name]) {
if (net.family === 'IPv4' && !net.internal) {
console.log(- ${name}: ${net.address});
}
}

sooo, there is this annoying issue with docker and stdout buffering

tldr: if the app doesn't flush the buffer, the logs can appear god knows when

and this looks like node (I assume you're using it) is getting fucky because of whatever reason

yes node. not sure how to "flush the buffer", but its something to figure out and try. thank you

you can try to just log a ton of nonsense to overwrite that 4KB buffer… but again, it seems like the app actually prints those http requests just fine

agreed

the logs issue is driving me insane

level 1 tech support says to write better code

@ChicagoPhotoShop stop shitting on other people. This is a skill issue on your part and the Railway team have better things to do then help people troubleshoot someone elses code problems…

@Ayush I'm not shitting on other people. this is a support forum, I'm seeking support. I'm not the only one having this issue. railway has nearly zero documentation and the only support provided is "write better code". go back to what rock you came out from

@ChicagoPhotoShop - "I'm sorry you're facing difficulties with your code, but we are only able to offer support for the Railway platform here"

I get it, you must be frustrated with your vibe coding issue, but being rude isnt the right way to go about it.

ah. railway status is green. sorry, cant help ya. 👍🏻

you tell me to stop shitting on people, and they you come here shitting on me. seriously, go smell some grass

<:kekw:788259314607325204>

douche

Relax bud, you just need some accountability. All of a sudden, when someone calls you out, then you get defensive and start throwing insults. No one's stopping you from venting, but if you're looking for help, maybe drop the attitude and focus on the issue at hand.

calls me out for what?

seeking support?

im calling you out for being rude and shitting on the railway team even though its not their responsibility?

happy to focus on the issue at hand. what is it that you are doing exactly? seriously, go somewhere else

you are calling me out for being rude while being rude yourself. pot meet kettle. go away already christ

You came in here whining, got called out for being rude, and now you're deflecting instead of owning up to it. If you actually want help, act like someone people would want to help. Anyways, I'm done here, good luck 😂

you promise?

what;s up

still the "no logs" issues?

i do not get console.log() on railway, thats correct. but it doesnt seem like its supported here so I'm moving on. I can see all the logs I need when working locally.

is your app loaded from a docker image?

yes

ok

im ready

i'm not an english native, so if you don't understand something I say, let me know to paraphrase myself

indeed, this is all about flush

I made a repo in python, but you can easily translate it to js since it's just a oneline change

when you deploy from docker, it doesn't flush your strings in railway. In a few words, your content is waiting in a buffer before being served

you can force it to be flushed and then the text will appear

changing your code from

to

what else can make the trick? Adding a jump in your printed or consoleloged text: \n

so here

i can see the printed text

I'm testing and it works. But doesn't seem to work with the char \n in my case and it waits till the next flushed print

Most of the server aren't 🤣

so I'm getting these messages swaped

Thing is, node does flush its console logs by default

Unless something goes wrong with it

python does it too, except when it doesn't 😆 soyou have to force it

well. Adding flush to every print fixes the issue for me and now I got the logs in the correct order

it also works fine from CLI

and my web site shows glamorously

before this, just the error logs were printed. So if you change console.log to console.error, it should work as well

sadly, what @maddsua seems to be right ):

I don't have experience with node, but I had the same issue in python and I solved it in this way. Maybe it's a docker thing, so you could try to run without it or use console.error instead

I hope it helps you, @ChicagoPhotoShop

Yeah, docker has buffered io for stdout but not stderr

this is great, thank you @patod01 what does your railway logs panel look like?

But again, they seem to have those http logs printed just fine

I tried console.error too

To no avail?

ironically it works for my backend deployment, not frontend

Bruh

Damn node!

if those came from the framework, that may be the reason. I use bottle in python, and the logs in debbug mode were made through other way but print and I have zero lines of code to print the http response codes, so my normal prints didn't work while the logs from bottle did

Nope, it's this

ah… I'll see it

That's what I was told anyway

Ehh just use golang at that point xD

it looks like this

no idea of why that gets printed. Maybe is for the strings being made by a back tilde (`) instead of " or '?

Shouldn't make any difference

I will blame the framework :v

I googled it and I came to the idea of maybe there's an environment var for node that works the same as the case described in the picture for python

in case this helps, here is the repo https://gitlab.com/patod01/test-docker. It also has an image you can pull and test from [registry.gitlab.com/patod01/test-docker](registry.gitlab.com/patod01/test-docker)

Gitlab mentioned <:lfg:786867302888505364>

there is nothing wrong with buffers or anything like that.

They have a Dockerfile with this -

CMD ["sh", "-c", "serve -s build -l ${PORT}"]

fwiw they aren't setting a start command elsewhere, serve is the only program being ran.

<:wat:786868710791053312>

I can't read greek

Brody got annoyed and peeked into the code

yep annoyed since the blame was placed onto the platform

What's in the name of everything that's holy is that

alright, y'all got this now, peace

You won't even post a correct version of the command?

@Brody blame wasnt on "the platform". I was asking for help and only response was write better code.

in brody's defense, he was right. He should't help in code cases 'cause it may be to hard to point out where the problem could be in the code

I understand. but not everyone is a pro, and there is no where else to go for support. never was I "blaming" railway. simply asking how it works. something like, "maybe something wrong with docker build" would have helped alot

i understand what you say, but you overstated here what brody said

and seemed like you were very angry for so little

To be fair the docker file run cmd is… Unusual

CMD ["/app/[start.sh](start.sh)"]

in any case, idk if this is pro league if we are dealing with bufffered stuff and docker files. I understand that railway is meant for business, so you need some pro background. Not 100%, but something at the end of the day

What's inside the start.sh

what matters now is that you have plenty material to keep your research! and we know that you have everything to make it work 😄

Shell scripts can be real fucky when used as launchers

great

try running node directly

this is my cmd in the docker file CMD source ../.venv/bin/activate && python [rock.py](rock.py) $MODE $PORT

when you run shell scripts, you change the scope where the process is running

ok, changing it

I apologize @Brody for letting frustration get the best of me. been a long week.

!s