they said they tried to fix it

didnt work

<:anguish:936107845039054868>

maybe we can get nerd @nebula to fix it

what is a ws server? my app's calls are very short

you're hosting a ws server

right

so that breaks basically

because of how railway handles thnigs

ws = web service? are all railway sites ws?

hi

WebSockets

fix it

!!!!

You need to use an external WebSocket service such as socket.io or link a domain. By default our proxy will terminate long lived connections for scale reasons.

https://help.railway.app/troubleshooting/hKqw9Dr1moxfDySTy98E6G/websocket-connections-disconnecting/sb6bfjV6UnuMwkRyAvQ3Sb

yeah but that's not fixing the issue lol

it's a work around

We have a fix in progress (Charith is on it) but we need to wait until Private Networking first until we can start opening up non-HTTP traffic on long lived connections (ws://, tcp:// etc)

!!! woo hoo

I guess I don't understand about sockets and long lived connections. I didn't think my site was using sockets

all my calls are https

According to your logs you do, what is your code trying to do?

can you share your package.json

it makes occasional api calls initiated by the user, receives a response, and processes it. calls never take more than a second

i think i know whats wrong

sure one sec

1067143022480982026

yup so you're running react in dev mode

i set NODE_ENV = production

yep, but your start script is launching the dev server

that d oesnt change anything

add serve as a dev dependancy

so npm i -D serve or yarn add -D serve

Staticfile provider 🚀

nah staticfile is wonky

lmao

actually i guess that could work

but its still weird

serve is easier imo

idk why we built staticfile

it's not very god

installing serve now. do i need to change the start script to something else?

yes, change it to serve -s build

also set the PORT environment variable to 3000

you might also want to add a dev script set to react-scripts start to preserve the old behavior during development

on it! tyvm… will let you know if it all works

Okay, I installed serve, updated some npm packages, updated start script, added dev script, added PORT=3000 and redeployed. I no longer get the socket error message. I do notice the Deploy log shows activity whenever I load the page or do a user-initiated api call. Is this normal?

yes

Sweet. Thanks again for the quick help

Hey Angelo. This help article does not seem to exist anymore. Do you have any other reference?

Are you facing the same issue?

Yes. Im facing the same issue. I'm using express. This is part of my code on how it is set up.

const httpServer = createServer(app);

const io = new Server(httpServer, {
  cors: {
    origin: "*", 
    methods: ["GET", "POST"],
  }
});

....
const PORT = process.env.PORT;
  httpServer.listen(PORT, () => {
    console.log(`Server running on port ${PORT}`);
    io.attach(httpServer);
  });

Are you using a default Railway domain?

could you also show the error you get in your console?

Definetely. Thanks for the help btw. To answer the questions:

1. I'm using the railway default domain for my dev code. I also have a custom domain configured with railway for my prod version.

2. This is the error in the console:

websocket.js:43 WebSocket connection to 'wss://api.noisse.io/socket.io/?EIO=4&transport=websocket&sid=NKUyJEI5p-soqJdaAAA-' failed: 

looks like that error is a bit cut off?

This is the complete error message:

WebSocket connection to 'wss://api.noisse.io/socket.io/?EIO=4&transport=websocket&sid=9lioIEtnQSRL-L1xAABM' failed: 
value @ websocket.js:43
Show 1 more frame
Show less

thats unfortunaly not complete, can you link to a page where i could see this error for myself?

I can add an screenshot of my console output. Btw, english is not my first language, so if I'm not explaining myself well let me know.

This is the full code for websocket.js

1220433941295792270

The error falls here: : new WebSocket(uri)

all im seeing is failed: with no error message, this isnt super helpful unfortunately, maybe you could look for extra clues in the network tab?

maybe this is a CORS or similar error in disguise?

I will investigate further. I will check cors as well. I will reach out with an extra message if I found a helpful error or a solution in case others find it useful.