404 response code: not able to connect to the asyncio server deployed in testing environment

[nsrawat009]

I have deployed asyncio server in one of the testing environment of my firm successfully but iam not able to make connection to the server with Postman or python client although i was able to connect and get response successfully in my local testing.I dont know it is the issue with routing or incorrect url.
Iam unsure about the socketio_path arguement in ASGI app,whether i have to provide it or not since bydefault it takes socket.io path whether it should I define it inside sio_app or not??

#intializing socketio server
sio = socketio.AsyncServer(
    async_mode='asgi',
    cors_allowed_origins=['*'],
    ping_timeout=6000,   
    ping_interval=12000,
    logger=True,
    engineio_logger=True
)

sio_app = socketio.ASGIApp(
    socketio_server=sio,
    other_asgi_app=app,
    static_files = {
    '/static': './public'
}
)

Note:here app is another fast api app dedicated for rest endpoints

#Event handler to connect client to socketio server
@sio.event()
async def connect(sid, environ):
    logger.info('user trying to connect')
    username = environ.get('HTTP_X_USERNAME')
    logger.info(f"user trying to connect: {username}")
    if not username:
        return False
    async with sio.session(sid) as session:
        session['username'] = username
    await sio.emit(event='user_joined',data=username)



@sio.on('recommend_gsi',namespace='/paragraph_grammar/gsi_suggestions')
async def gsi_recommendation(sid: str, data: Dict[str, Any]):
    logger.info("GSI Recommendations through socketio API")
    # Extract authorization and accept-language headers from data
    try:
        # Extract authorization and accept-language headers from data
        gsi_collection_headers = {
            "Authorization": data.get("Authorization"),
            "accept-language": data.get("accept-language", "en").lower()
        }

---

is my url correct??: (ws://nebula.nslhub.com/dsd-orch/paragraph_grammar/gsi_suggestions
Note: nebula.nslhub.com is the dns name of the environment
dsd-orch is the security layer
/paragraph_grammar/gsi_suggestions is the namespace of the event
Also i have not implemented ssl configuration yet.

Note in my microservice the request comes via istio -> kubernetes pod -> microservice -> end point

Currently iam getting 404 response code I will try removing static files which i have currently provided.What else should i check,Kindly support iam stuck

[miguelgrinberg]

Socket.IO is a bit strange in how the URL is specified.

The connection URL should be your hostname followed by your namespace. So try using ws://nebula.nslhub.com/paragraph_grammar/gsi_suggestions.

The path to the Socket.IO endpoint is given in the path argument, which I think in your case should be /dsd-orch/socket.io.

If this does not work, you should probably try to make your HTTP endpoints work first, then adapt your url and path accordingly.

[nsrawat009]

sio_app = socketio.ASGIApp(
socketio_server=sio,
socketio_path="/dsd-orch/socket.io"
other_asgi_app=app,
static_files = {
'/static': './public'
}
)
I kept socketio_path="/dsd-orch/socket.io" as you suggested before and sample url for REST requests is https://nebula.nslhub.com/dsd-orch/paragraph_grammar/extract_bpmn
Here: paragraph_grammar is the microservice deployed in kubernetes pods and extract_bpmn is the HTTP endpoint
whereas in the socketio case i tried to hit
ws://nebula.nslhub.com/dsd-orch/socket.io/paragraph_grammar/gsi_suggestions
ws://nebula.nslhub.com/dsd-orch/paragraph_grammar/gsi_suggestions
ws://nebula.nslhub.com/paragraph_grammar/gsi_suggestions
Here :paragraph_grammar/gsi_suggestions is the namespace
but all are failing to connect with Postman(websocket and socketio both tried) and python client iam getting folowing error in python client
User
Attempting WebSocket connection to ws://nebula.nslhub.com/dsd-orch/socket.io/?transport=websocket&EIO=4
Connection error
Failed to connect: Connection error
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7377b861cd00>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7377b860d720>, 6060.1061981)]', '[(<aiohttp.client_proto.ResponseHandler object at 0x7377b860e4a0>, 6060.2374707)]']
connector: <aiohttp.connector.TCPConnector object at 0x7377b861cdc0>

[miguelgrinberg]

Any difference if you remove path in the server, but keep it in the client?

[nsrawat009]

After doing cahnges in dsd-orch repo my request is reaching the service now but getting GET 404 not found error not sure its the socketio server throwing that error or the fastapi server how can I verify that and how to resolve that.

[nsrawat009]

not mentioning path in the server is not working at all when i kept /dsd-orch/socket.io in path arguement atleast request is reaching the pod

[miguelgrinberg]

Unfortunately I'm not sure how I can help more with this. You see that this is clearly a routing problem. If the requests reach the Python process, then it is a matter of looking at what the URL that is received in Python looks like, and then setting the path argument in the server to make sure the URL is a match. That's really all there is to it, but you'll need to add some logging in the ASGIApp class to see the URL.

In case it helps, here is the place where the Socket.IO routing logging happens (in the python-engineio package): https://github.com/miguelgrinberg/python-engineio/blob/main/src/engineio/async_drivers/asgi.py#L64-L67. Once you know what URL arrives at the Python server, you just need to set socketio_path (called engineio_path in the lower level code I linked) so that the condition in this if-statement is true, which will forward the request to the Socket.IO logic.