[ctrl] close. code: 4000 Invalid Domain (credentials)

[asferrer]

Hello everyone,

I have successfully deployed the same web application on two Windows servers, each with its own active Streamedian license and domain. However, we are currently facing a playback error on one of these servers that is preventing video stream visualization.
The specific error, as identified in the web app's console during inspection, is:

This issue is not present in our other server deployment, and the RTSP stream is accessible through VLC on the affected server, which indicates that the issue is isolated to the Streamedian configuration or its interaction with our server setup.

Here are some additional logs from the Windows Powershell, because our server is a Windows Server 2022:
Checking the Event Viewer from the server, at first we had an application error log as follows:

    Log Name:      Application
    Source:        Application Error
    Date:          3/7/2024 5:51:21 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ewaaegviif00.enelint.global
    Description:
    Faulting application name: websock_rtsp_proxy.exe, version: 0.0.0.0, time stamp: 0x62436140
    Faulting module name: websock_rtsp_proxy.exe, version: 0.0.0.0, time stamp: 0x62436140
    Exception code: 0xc0000005
    Fault offset: 0x00000000000c83ce
    Faulting process id: 0x1c10
    Faulting application start time: 0x01da70a5c7404152
    Faulting application path: C:\Program Files\Streamedian\WS RTSP Proxy Server\websock_rtsp_proxy.exe
    Faulting module path: C:\Program Files\Streamedian\WS RTSP Proxy Server\websock_rtsp_proxy.exe
    Report Id: c0907593-2eeb-4c6a-b3ee-cc4fb8117db1
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>100</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2024-03-07T16:51:21.9825745Z" />
        <EventRecordID>14842</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>ewaaegviif00.enelint.global</Computer>
        <Security />
      </System>
      <EventData>
        <Data>websock_rtsp_proxy.exe</Data>
        <Data>0.0.0.0</Data>
        <Data>62436140</Data>
        <Data>websock_rtsp_proxy.exe</Data>
        <Data>0.0.0.0</Data>
        <Data>62436140</Data>
        <Data>c0000005</Data>
        <Data>00000000000c83ce</Data>
        <Data>1c10</Data>
        <Data>01da70a5c7404152</Data>
        <Data>C:\Program Files\Streamedian\WS RTSP Proxy Server\websock_rtsp_proxy.exe</Data>
        <Data>C:\Program Files\Streamedian\WS RTSP Proxy Server\websock_rtsp_proxy.exe</Data>
        <Data>c0907593-2eeb-4c6a-b3ee-cc4fb8117db1</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

Here are some references to open issues, which all of them were followed and none of them solved the problem.
#177 #154 #134 #115

[asferrer]

Solved because there was an issue with the wss:// redirection on my webapp source code