Change listening port of Chroma SDK

Discussion in 'Razer Chroma' started by mrgummage, May 18, 2017.

Thread Status:
Not open for further replies.
  1. mrgummage

    mrgummage New Member

    I use my BlackWidow Chroma and Naga Hex with my work laptop when at home and installed the SDK so the backlights would work, unfortunately the Chroma SDK binds HTTP.SYS to port 80 which prevents my local Apache server from loading.

    I understand it's an edge case but is it possible to change what port the SDK binds to so I can have my backlights and Apache server?
    PraaqNiickk and storm.climax like this.
  2. njbmartin

    njbmartin Well-Known Member

    Razer are aware of this and are in the process of updating the API to use a different port.
    PraaqNiickk and arnoldwender like this.
  3. Do we have an ETA on this? I have to uninstall until it is fixed.
  4. okonietoperza

    okonietoperza Active Member

    @baileyh for the time being, launch task manager, go to services tab and stop the Razer Chroma SDK Server (don't confuse it with Razer Chroma SDK Service). Also right-click it, "open services" and disable it there so it doesn't autostart on your next boot
    arnoldwender and baileyh like this.
  5. arnoldwender_no_id

    arnoldwender_no_id New Member

    Thanks, that fixed my issue so I can go back to work... I hope Razer fix this A.S.A.P.!
  6. njbmartin

    njbmartin Well-Known Member

    Hey gang. Synapse got an update today. It should be on a new port "54235". Let me know if you've got the update and it's on the new port.
  7. okonietoperza

    okonietoperza Active Member

    Thanks for the heads-up! Indeed nothing running on port 80 anymore, and *something* running on port 54235 :)

    PS C:\WINDOWS\system32> netstat -n -b -a | Select-String -Pattern '(TCP|UDP)\s+[0-9.]+(:80|:54235)' -Context 0,1
    >   TCP              LISTENING
       Can not obtain ownership information
    I've noticed the changelog on hasn't been updated yet, any other big changes in this release since 2.1.5?
  8. njbmartin

    njbmartin Well-Known Member

    That was the only change I believe.
Thread Status:
Not open for further replies.