Websocket connection failed
Hi Team,
I asked this question on behalf of one of our customers in Hong Kong, who is testing RTMDS. They tried to connect to
ws://159.220.108.207:8101/WebSocket
ws://159.220.108.207:8101/hEDD
but they encountered an error during handshake: 'connection was forcibly closed by the remote host'.
They are now asking whether RTMDS server has restrictions on client's IPs?
And could you also advise how to resolve this?
Thanks,
Leo
Best Answer
-
Hi @leo.wu01
As my colleague pointed out, port 8101 is not the normal Websocket Port - certainly on RTMDS I would expect it to be configured as 15000.
Can you confirm if they are seeing the above error using a working Websocket API example such as websocket-api/market_price.py at master · Refinitiv/websocket-api (github.com) - with the correct port 15000?
If so, this question is best directed to the RTMDS team - as they would know best about restrictions etc or why the connection is forcibly closed.
0
Answers
-
Hello @leo.wu01 ,
Is the client connecting to their local RTMDS via websocket?
If yes, would suggest to confirm with their local Market Data admin/team if this is the correct IP address, and port to connect (default websocket port for ADS/RTDS connection is 15000, whereas 8101 is the default legacy SSL port) and if websocket connectivity is enabled on the local RTDS - it is not mandatory to enable websocket connectivity on RTDS.
Please see Websocket API: Quick Start - Connecting to Refinitiv Real-Time Distribution System for quick step-by-step on how to connect.
0 -
Hi @leo.wu01
I would also recommend the customer actually work through some basic Websocket API tutorials - it will save them much time in the long run.
0 -
Hello @leo.wu01
While my colleagues already provided insightful information about the WebSocket port and resources that the client can check further, the client's Market data team can use the RTMDS testclient tool to verify the WebSocket connection too.
Please see more detail on this How to test the WebSocket connection with the Infrastructure testclient tool article.0 -
Hi @umer.nalla @zoya faberov and @wasin.w
Thanks to all of you! I have sent your recommendations on port number and those useful links to customer.
Regards,
Leo
0 -
Hi @Jirapongse ,
All these answers are very useful, and I have already sent these links and the recommendations to the customer.
Thanks,
Leo
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛