Chat callback not returning data.

What is the full version of the chat plugin you're using?

404 to /socket.ashx/ is truly strange. Is the user still authenticated when that happens? Possible to collect a HTTP trace of when it happens, concurrent with a diagnostic export?

The bus shouldn't be directly related.

on page refresh, this is the last section of requests
Chat version:  2.0.0.384
Platform version is the latest 10.3.6.12348 hotfix

Would it be possible to share a full diagnostic export? Maybe via private message?

I'm going to install 10.3.6 OOTB and try merge in all of our changes.

Let me know how it goes. If you run into the 404s though, please do share a diagnostic, especially spanning a time frame that included an app restart.

OOTB 10.3.6 works just fine.  I'm going to merge changes in now to try find the culprit.

Thanks for the help.

Update.  We are using Microsoft AAD for authentication with a OWIN Middleware component.  When I turn it on, we get a 404, when I disable OWN, the 404 goes away...

 <add key="owin:appStartup" value="AADAuth" />

This would make sense. The platform registers itself against OWIN's startup to initialize SignalR. This may not currently be a supportable way of extending authentication. Does AADAuth need be implemented as OWIN middleware? Is it possible to use IAuthenticationPlugin or IExternalAuthenticationPlugin for your needs?

The Dual stack authentication we're using, as far as I know, requires OWIN middleware, but I'll keep looking.

I wonder if I could initialize SignalR in my own startup?  Is it worth a try?

Luke R Davidson said:

initialize SignalR in my own startup

Not in a supportable way, since it requires initializing SignalR against an internal handler implementation. SignalR, itself, isn't an extensibility point in the platform; it's just part of the implementation for ISocket plugins.

Luke R Davidson said:

initialize SignalR in my own startup

Not in a supportable way, since it requires initializing SignalR against an internal handler implementation. SignalR, itself, isn't an extensibility point in the platform; it's just part of the implementation for ISocket plugins.

First of all, I know this is 100% NOT Supported, but I did manage to get it working.  I created a third OWIN startup class whose job it was to run through all loaded assemblies, find other OWIN startup classes and invoke them.  This seems to have done the trick and both are up and running.  My auth works and the chat/sockets work now.

 [assembly: OwinStartupAttribute(typeof(MasterStartup.Startup))]
namespace MasterStartup
    {
        public class Startup
        {
            public void Configuration(IAppBuilder app)
            {
                foreach (Assembly startupAssembly in System.AppDomain.CurrentDomain.GetAssemblies().Where(assembly => assembly.GetCustomAttribute<OwinStartupAttribute>() != null))
                {
                    OwinStartupAttribute startupAttribute = startupAssembly.GetCustomAttribute<OwinStartupAttribute>();
                    if (startupAttribute.StartupType != typeof(MasterStartup.Startup))
                    {
                        object startupClass = Activator.CreateInstance(startupAttribute.StartupType);
                        string startupMethod = string.IsNullOrEmpty(startupAttribute.MethodName) ? "Configuration" : startupAttribute.MethodName;

                        startupAttribute.StartupType.GetMethod(startupMethod).Invoke(startupClass, new object[] { app });
                    }
                }
            }
        }
    }