Razer Chroma SDK Server is blocking port part 2 | Razer Insider
Skip to main content

Razer Chroma SDK Server is blocking port part 2

  • December 3, 2019
  • 4 replies
  • 211 views
S
Hi there, I'm using Razer Basilisk since yesterday. After installing Razer software (Synapse), I recognized that the port (1337) I usually use for development is blocked. Unfortunately it is the Razer Chroma SDK Server. Is there a way to define which port it should use? This problem has been postet before and still persists (/razer-chroma-sdk-server-is-blocking-port.51071/). Any chance of solving this issue? Ports for daily work > Razer software
Did this topic help you find an answer to your question?
This topic has been closed for comments

4 Replies

P
I would also like to change the port.
Razer.Speedcr0ss
suxxez
Hi there, I'm using Razer Basilisk since yesterday. After installing Razer software (Synapse), I recognized that the port (1337) I usually use for development is blocked. Unfortunately it is the Razer Chroma SDK Server. Is there a way to define which port it should use? This problem has been postet before and still persists (/razer-chroma-sdk-server-is-blocking-port.51071/). Any chance of solving this issue? Ports for daily work > Razer software
Hi there! Thanks for posting your Razer Synapse related concern on our Support board. By the way, how did you learn that your port 1337 has been blocked? Please send me a PM together with a video or screenshot showing this behavior.
P
Razer.SpeedCr0ss
Hi there! Thanks for posting your Razer Synapse related concern on our Support board. By the way, how did you learn that your port 1337 has been blocked? Please send me a PM together with a video or screenshot showing this behavior.
I first noticed it when I tried to start a nodejs server at port 1337. It automatically changed to 1338 instead, because 1337 was in used. I used netstat to get the id of the process using the port and then tasklist to get the process name: (*Removed for security purpose)
Razer.Speedcr0ss
palpie1980
I first noticed it when I tried to start a nodejs server at port 1337. It automatically changed to 1338 instead, because 1337 was in used. I used netstat to get the id of the process using the port and then tasklist to get the process name: (*Removed for security purpose)
Thanks for letting me know. I replied to your PM. I'll wait for your response.
CookiesCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings