SignalR Hub doesn't load when Umbraco is installed in subfolder of site (breaks preview updates?)

[KevinJump]

If you install Umbraco in a SubFolder (not sure if this is 'supported'?) - then any requests for the signalR hub fail. http://localhost/subbraco/umbraco/BackOffice/signalr/hubs returns a 404.

• This breaks the SignalR based refresh methods in page preview

Umbraco version

I am seeing this issue on Umbraco version: 8.6.2

Reproduction

• Install umbraco in a subfolder of IIS
  • (downloaded zip package)
  • with base starter kit
• in backoffice - go to homepage click preview
• view browser console to see signalR load errors

Cause ?

I suspect this is something to do with how the signalR hub is initialized. in appBuilderExtensions
( https://github.com/umbraco/Umbraco-CMS/blob/v8/contrib/src/Umbraco.Web/AppBuilderExtensions.cs#L53 )

but I can't immediately see why.

I have tried to a couple of other locations to see if it's registered somewhere else.
All these still fail. (and are guesses anyway)

• subbraco/backoffice/signalr
• subbraco/signalr/hubs
• subbraco/umbraco/signalr/hubs
• subbraco/signalr/js (the signalR default)

[nul800sebastiaan]

Hi @KevinJump! Do you have the errors you're talking about somewhere?

It looks like the initialization is done with respect to the configured path (appSetting: Umbraco.Core.Path) so hopefully should work, did you set that one?

Did you configure subbraco somewhere? And I assume this is a virtual directory?

[KevinJump]

I'll go check ! (not my setup)

[umbrabot]

Hiya @KevinJump,

Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.

We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).

To open it this issue up again, you can write @umbrabot still relevant in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.

For example:

@umbrabot still relevant
This bug can still be reproduced in version x.y.z

This will reopen the issue in the next few hours.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂