Activities of "Riaan.Smit"

Hi @ismcagdas,

Thank you for the follow up and all the help. I got the problem resolved on Monday. It was basically all related to the nginx server configuration. After spending a few hours with my server team, we got the config sorted and the signalr functionality worked 100%.

Hi @ismcagdas,

So I know why I'm getting the weird syntax error. If I check the url for any of the signalr endpoints, I'm getting the 404 html page back.

Navigating to any of the signalr urls produce a 404 page. I'm not sure if I deployed the server portion of the project correctly?

https://psecportalapi.prescient.co.za/signalr-chat/negotiate

Hi @ismcagdas,

I just sat with my server team and confirmed the reverse proxy settings and it seems like the websocket connection issue might be resolved. However, now I'm getting 100ds of "Cannot start the connection using ServerSentEvents transport. Unexpected token < in JSON at position 0" errors in the chrome console. And none of the .json files have any '<' characters in....any ideas where I can find what is causing the exception. Sorry I know this is super generic.

So I updated the abp packages to the latest version yersterday and did a fresh release. The error seems a bit different today. It seems like the end poinjt is getting reached, eventhough the handshake still fails. If I execute a POST request with the url in Postman, I get a 200 response though.

<handlers>
	<remove name="WebDAV" />
	<remove name="ExtensionlessUrlHandler-Integrated-4.0" />
	<remove name="OPTIONSVerbHandler" />
	<add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />	  
</handlers>

Great, thanx for the confirmation.

Hi,

What is the correct version of SignalR I have to be on for the .NetCore + Angular 7 project?

Am I on the correct version: Angular: "@aspnet/signalr": "^1.1.4" .NetCore: Abp.AspNetCore.SignalR v4.9.0

Regards, Riaan

Hi @Ismcagdas,

Thank you for the reply. I tried everything I've read regarding server configuration, and after replacing the actual statup cors code with : builder .AllowAnyMethod() .AllowAnyHeader() .AllowAnyOrigin();

I'm still getting the same "No 'Access-Control-Allow-Origin' header is present on the requested resource" error on /signalr/negotiate

Am I correct in assuming that this error might have nothing to do with the Cors setup in the startup routine? I'm completely out of ideas.

So after reading up about nginx and signalR, I asked my server team to update the server config with the details as described in the following post (https://kimsereyblog.blogspot.com/2018/07/signalr-with-asp-net-core.html at #4)

No I'm getting a CORS policy failure on the signalR comms. I've also updated the appsettings.Production.config file to include the signalR hub enpoints:

"CorsOrigins": "https://psecportalapi.prescient.co.za,https://psecportal.prescient.co.za,https://psecportalapi.prescient.co.za/signalr-chat/negotiate,https://psecportalapi.prescient.co.za/signalr-equityDesk/negotiate"

Any ideas?

Hi,

I'm working on an Angular + .Net Core project. The SignalR functionality works in my debug environment. However, it doesn't work at all in production. The production environment runs in IIS behing a nginx reverse proxy (which I'm not sure if the problem lies there).

I'm not even sure where to start looking for the problem. Any suggestions would be much appreciated.

Thank you for the quick response!