signalr and azure #1823

6 Answer(s)

• 

  0

  ismcagdas created 8 years ago

  Support Team

  Hi,

  Did you deploy on a VM ? If so, you can check Logs.txt (under your iis site folder) for more error details.
  Otherwise you can check Azure's logs to see error details.

  It might be a configuration issue.

  Save Cancel
• 

  0

  joshyates created 8 years ago

  I looked into the logs. The 500 error in my azure environment: D:\home\site\wwwroot\signalr\negotiate

  http://testsite:80/signalr/negotiate?clientProtocol=1.5&connectionData=%5B%7B%22name%22%3A%22abpcommonhub%22%7D%2C%7B%22name%22%3A%22chathub%22%7D%5D&_=1476798018491
  

  Does it have anything to do with ABP platform? I could not find anything in the ABP SignalR documentation about deployment.

  I have monitored my azure web app: <a class="postlink" href="https://azure.microsoft.com/en-us/documentation/articles/web-sites-enable-diagnostic-log/">https://azure.microsoft.com/en-us/docum ... ostic-log/</a>

  Copy the code below, paste in notepad and save as error.html to view:

   
   
   
   
   
   
   
   
   
   
  HTTP Error 500.0 - Internal Server Error
   
  The page cannot be displayed because an internal server error has occurred.
   
   
   
  Most likely causes:
   
   	
  IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
   	
  IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
   	
  IIS was not able to process configuration for the Web site or application.
   	
  The authenticated user does not have permission to use this DLL.
   	
  The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
   
   
   
   
   
  Things you can try:
   
   	
  Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
   	
  Check the event logs to see if any additional information was logged.
   	
  Verify the permissions for the DLL.
   	
  Install the .NET Extensibility feature if the request is mapped to a managed handler.
   	
  Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. 
   
   
   
   
   
   
  Detailed Error Information:
   
   
   
  Module
     AspNetCoreModule
   
  Notification
     ExecuteRequestHandler
   
  Handler
     aspNetCore
   
  Error Code
     0x00000000
   
   
   
   
   
   
  Requested URL
     http://testapp:80/signalr/negotiate?clientProtocol=1.5&connectionData=%5B%7B%22name%22%3A%22abpcommonhub%22%7D%2C%7B%22name%22%3A%22chathub%22%7D%5D&_=1476798018491
   
  Physical Path
     D:\home\site\wwwroot\signalr\negotiate
   
  Logon Method
     Anonymous
   
  Logon User
     Anonymous
   
   
   
   
   
   
   
   
   
  More Information:
   
  This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error. 
  View more information »
   
  Microsoft Knowledge Base Articles:
   
    
   
   
   
   
   
  
  

  Save Cancel
• 

  0

  joshyates created 8 years ago

  The 500 error is caused because of path location? SignalR is caught in a GET loop trying to connect, but is not targeting the correct path within Azure:

  http://testapp:80/signalr/negotiate?clientProtocol=1.5&connectionData=%5B%7B%22name%22%3A%22abpcommonhub%22%7D%2C%7B%22name%22%3A%22chathub%22%7D%5D&_=1476799379443
  

  Save Cancel
• 

  0

  ismcagdas created 8 years ago

  Support Team

  Hi,

  We haven't faced such a problem when deploying to azure.
  Your problem seems like a security or configuration issue.

  I have found this one when searching about your problem <a class="postlink" href="https://github.com/SignalR/SignalR/issues/3659#issuecomment-247773451">https://github.com/SignalR/SignalR/issu ... -247773451</a>
  Can you try to do that ?

  Save Cancel
• 

  0

  joshyates created 8 years ago

  Should the url be my server url? <a class="postlink" href="http://www.website.com:80/signalr/">http://www.website.com:80/signalr/</a> instead of <a class="postlink" href="http://website:80/signalr/">http://website:80/signalr/</a>

  I took a screenshot of my trace in my Azure environment:

  

  Save Cancel
• 

  0

  joshyates created 8 years ago

  Logs from azure server:

  ERROR 2016-10-21 12:42:21,610 [28   ] e.Diagnostics.ExceptionHandlerMiddleware - An unhandled exception has occurred: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.
  System.Security.Cryptography.CryptographicException: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.
     at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
     at System.Security.Cryptography.DpapiDataProtector.ProviderProtect(Byte[] userData)
     at Microsoft.AspNet.SignalR.Infrastructure.DataProtectionProviderProtectedData.Protect(String data, String purpose)
     at Microsoft.AspNet.SignalR.PersistentConnection.ProcessNegotiationRequest(HostContext context)
     at Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext context)
     at Microsoft.Owin.Mapping.MapMiddleware.d__0.MoveNext()
  

  Save Cancel