N/A

Railway doesn't support UDP yet

what can I use instead of railway for UDP?
by Yet, should I wait? Or do it?

I'm not sure, I only use Railway so

I'd say it's worth waiting, unless you're in a hurry

well depends how long they take to do it, i wouldnt mind funding their research into implementing it.
I love railway, would be sad to not use it, for one reason.

it cant hurt for me to ask, how much would you pledge

I would put the money in depending in how long it takes to do it. I would need a time scale before I can estimate the pledge

As I said, I would do it for the cause. Just need to know for my sake, as a game developer as well

considering its not currently on the roadmap, it would have to be quite the sum of money

there have been recent threads about it

must be a thing that is starting to arise

right but there isnt spend to back up the asks

alright, how much would you request?

I dont want to set it too low, or too high. (Business 101)

we may be able to do it in the next quarter for a committed 100k spend, but im not the person who decided that stuff

damn, nah XD lost me there

cant donate 100k, can do like £50 lol

great, time to find a new service and migrate everything!

thanks for the support overall! Means a lot :D

unfortunately that wouldn't even get us talking about it, but i appreciate the sentiment

I have a compromise

I can use railway for my services and use something else for UDP

what other VPS could I use? (too lazy to migrate it all + already spent enough money on railway, i dont want to waste it)

what other VPS could I use? (too lazy to migrate it all + already spent enough money on railway, i dont want to waste it)

(still going to use railway as it does all the other stuff)
(UDP is seperate + the game servers)

i dont have any preferences, personally, if something doesnt run on railway I'd just build it differently until it can run on railway

can you give like a estimate of how long the team thinks it would take to implement, so i can have some faith

(and do what you suggest)

we dont have any plans to implement it to begin with

welp.

what are the reasons why outgoing is allowed but not incoming publicly?
(private incoming and outgoing is allowed, i know that)

we can't implement features without clear spend to back up the asks

outgoing udp traffic just works, we didnt need to do anything there, thats just how the internet works

incoming though?

we need to build a router for that

ah…

what if i build a virtual router? (im just yapping at this point)

google cloud services it is?

what if you build the server in a way that doesnt need udp

I'm making a realtime VR game so it requires low latency, if you can think of a way I can deliver data with low latency then please suggest!

websockets 🙂

I Can't for the life of me get my go socket to connect however… Which is strange as it all works and was double checked by several coders…

also isn't that http/https? (higher CPU bills)

yeah but once the connection is established and the upgrade made, then its just a data stream

I got python to work, but go doesnt for some reason work

which go is the language that is speedy and lightweight from what i know…

If I can get a low latency solution then there's no worry!

websockets and go work just fine on railway

alright amazing! just wanted to make sure

heyo! for the life of me, I cannot get websockets to work. There are no templates online, tried AI and it doesnt work, python overall is struggling, do you mind sharing some resources or code I could use for the server and client, secondly…

with this url what parts of it do we need?

wss://port-production-6c5f.up.railway.app:3004

As soon as websockets work even for a simple code we're good overall lol, just need something simple to go off as nothing is working

cc @Fragly

you cannot try to access your service on anything other than port 443

OH, great XD

alright let me try this again, if all else fails and i resort to throwing my computer out of a window, i'll come here!

damn, where have I gone wrong.

import asyncio
import websockets

async def connect():
    uri = "wss://port-production-6c5f.up.railway.app/ws"
    async with websockets.connect(uri) as websocket:
        msg = await websocket.recv()
        print("Server says:", msg)

asyncio.run(connect())

import asyncio
import websockets

async def handler(websocket):
    await websocket.send("Hello client!")

async def main():
    async with websockets.serve(handler, "0.0.0.0", 443, ssl=None):
        await asyncio.Future()

asyncio.run(main())

you shouldn't be listening on 443, listening on 3004 was fine, you just can't access the service publicly from 3004, you need to access the service publicly from 443

could you please share some code I could go from, I'm really lost
5 days of trying is finally hitting me

it's super simple, please just take the guidance I just gave

okay, I'll give it a shot! Else we'll see XD

if it still doesn't work, make sure your target port is set correctly

got it. (I hope, only deployment will tell)

Im really sorry if i'm just really bad at this and its super clear however I really dont know. Sorry :(

import asyncio
import websockets

async def connect():
    uri = "wss://port-production-6c5f.up.railway.app/ws"
    async with websockets.connect(uri) as websocket:
        msg = await websocket.recv()
        print("Server says:", msg)

asyncio.run(connect())

import asyncio
import websockets
import os

PORT = int(os.getenv("PORT", 3004))

async def handler(websocket):
    await websocket.send("Hello client!")

async def main():
    print(f"Listening on port {PORT}...")
    async with websockets.serve(handler, "0.0.0.0", PORT):
        await asyncio.Future()

asyncio.run(main())

Starting Container

Listening on port 8790...

again, to repeat, sorry :(

is your target port set correctly?

The port takes the OS port (server), unless I need to target a port in the client?

you need to set the target port in Railway

In the variables? Where sorry? The code?
Im somewhat blind at simple things

never overlook the docs -

there's a search bar for a reason 😉

AAAAAAAAAH!

oh, but i'm using the defualt generated domain?

you need to set it to the port your app is listening on

okay.. I'll try one last time

Lost all hope :(
and internal motivation

I know its simple and all, however i do request some sort of setup guide, or at least the code.
Im not letting the 5 days of struggle go to waste!!!

that's not the same domain that you just showed in your screenshot?

ooh… correct

timeout after timeout

your target port was still wrong, i fixed that for you, please try again

okay. so i just run the code on clientside?

yeah

dude…

Server says: Hello client!

YEAH!!!

another Brody W

what was the issue?

like as in the port > it was 3004 when i set it

your target port was wrong, for future ref -

there's a search bar for a reason 😉

Thank you tons!

really means a lot, knowing support is this active

imagine me when I'm not on my day off

Well thanks a ton

really means a lot haha

have a great one and dont forget to mark this as !s whenever you do it

slack and discord combined give me over 100 notifications a day according to android

crikey, buzzin life

https://open.spotify.com/track/6aV1TeadtXBsfvtxddXgqO?si=165cfb48dcce4628

!s