-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Once the negotiate function is hit i'm still not able to connect to the instance of signalR #1799
Comments
Where do you expect to start the connection? In Number1 looks like you are trying to start the connection from inside the Negotiate function. Could you describe your scenario a little bit more? |
@vicancy Thank you for the response the scenario can be like I need to access or open websocket mode for serverless on a particular page when the user clicks maybe a different route, to communicate with my angular frontend so to connect the signalR in my backend when i get the connection endpoint and access token i have a controller which handles the connection for signalR so there i create a new connection with the existing json i received from the negotiate function called. When tried with the controller it says For the response of negotiate function i called it explicitly from postman for testing in the above scenario |
I did a quick try on creating a
|
Describe the bug
i'm using signalR instance (serverless mode) i have created the bindings for signalR through the serverless framework, once the negotiate route is been hit i get the response but further when i try to connect with the same url and access token received from the negotiate function it gives error of
HubConnection failed to start successfully because of error 'Error: Failed to complete negotiation with the server: TypeError: Cannot read properties of undefined (reading 'secure')'.
To Reproduce
function.json:
Azure function handler (Number 1) i.e server.ts:
Azure function handler (Number 2) i.e server.ts:
Serverless.yml specification:
app.ts:
Exceptions (if any)
If azure handler is Number 1:
If azure handler is Number 2
Further technical details
"azure-functions-core-tools": "^4.0.5148",
"@microsoft/signalr": "^7.0.7",
The text was updated successfully, but these errors were encountered: