Skip to content
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

HTTPS/SSL issues #10

Closed
intelligentgoldfish-com opened this issue Mar 8, 2022 · 5 comments
Closed

HTTPS/SSL issues #10

intelligentgoldfish-com opened this issue Mar 8, 2022 · 5 comments

Comments

@intelligentgoldfish-com
Copy link

Hi! I've been pulling my hair over this for a while and thought I'd ask here. Cloned this repository into my project Plugins folder. Everything seems to work OK, but there's an error when negotiating with the signalr hub.

The hub is locally hosted (VS2022 Core WebApp), and works when using a browser with the same url. Both http and https. UE log gives me this error about SSL certificate:

image

Any ideas on how to solve this?

@intelligide
Copy link
Contributor

I don't think libcurl uses the Windows certificate store. Try disabling ASP.NET Core HTTPS redirection in your development environment.

@intelligentgoldfish-com
Copy link
Author

Yeah, I already tried that...without success!

@intelligentgoldfish-com
Copy link
Author

Unchecking this checkbox makes the error disappear, but there's still no connection established. OnNegotiateResponse() is never executed...

image

@julegault
Copy link

julegault commented Apr 26, 2022

i'm using the default chat hub example from microsoft, and the examples from this repo, and i'm getting the exact same error. Was the solution found ?

I can also confirm the delegate is never called.

@intelligide
Copy link
Contributor

intelligide commented Jul 26, 2022

I added a new troubleshoot section in the readme. Concretely, the problem comes from the fact that the functions are asynchronous and that the shared pointer removes the connection object and thus the connection with the server before the negotiation ended.
You just need to persist a reference to the connection object somewhere in your code to ensure that the object is not destroyed when the pointer is destroyed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants