(blazor) Failed to reconnect to the server #10325
Comments
Stamo-Gochev
changed the title
|
Some more info: Testing the same website on our staging server, I receive the following log when failed to reconnect: |
|
@mkArtakMSFT Please assign for investigation. |
|
@Stamo-Gochev This should only happen if the server gets shutdown or recycled. For example, in VS this can happen if you edit a C# file. VS will detect the file change and then restart the app. |
|
When testing using IIS Express (running from Visual Studio) I am not changing any of the code. The case is similar when hosting using IIS/Kestrel - what might cause the server to shutdown? Is there a way to handle the reconnection from the server? |
|
We're hosting this on IIS as well on the staging server, with the same results. Using the default app pool, without any specific configuration. The app is published with Release configuration. |
|
Is there any chance that the app was recycled in the staging environment when this happened? |
|
We will check if we can monitor the logs, and cross reference them with any dropped connections. Will write back as soon as we have a clear answer to this. |
|
The Log doesn't show any useful info. Here's a crash error: And here's the log from the staging server at that time: I had several tabs loaded, and they all crashed at the same time. Could you also clarify what do you mean by recycling the app - the pool or the app itself? The current setup is the app published to a destination folder, which is hosted through IIS. This is done only through a build, and the build is not triggered during the test period, when the crash happens. In other words the files of the hosted application are not modified at all. |
|
The findings so far show that the problem is caused by an (unexpected) restarting of the w3wp.exe process on our end (on the staging environment) and I am not able to reproduce the problem when the app is hosted on my IIS (by making sure nothing is modified, restarted, etc.). We will further investigate, but the issue seems to be caused by our environment. |
|
After further testing, it turned out that there are situations in which the testing environment needs to be shutdown, e.g. when installing updates, restarting the machine, etc., so is there a way to fix the "Retry" button functionality? I am not sure if the SignalR connection can be restored in these cases. |
|
@Stamo-Gochev The Retry button specifically tries to reconnect back to the state ("circuit") for the current UI session. Blazor doesn't provide an out of the box mechanism to persist and rehydrate this state, so after a server restart the state will be gone and no amount of retrying to connect to that state will help. Instead the user will need to refresh the browser. We have an issue open to make this clearer in the default UI (#10496). You can also customize this UI yourself: https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models#reconnection-to-the-same-server. Lastly, you should be able to do work in your app and components to support persisting the required state so that the app can survive a server restart. For example, the app could persist the circuit state into a memory cache, and the components could leverage local storage in the browser. We don't have great docs or samples on how to do this yet, but it's something we expect to provide before we ship. |
|
Thanks for the suggestions, We have already tried the customization of the "Retry" button to reload the page as this was the only thing that fixed the problem during testing. Still, we will test the ideas that will be added to the docs for restoring the circuit when they are out. |
|
I have this problem if i modify and save html file while running, the project is recompiled and browser try to refresh and says attempting to reconnect server.. but it wait just 2 secs and fail while solution is still compiling. If i hit retry it doesnt do anything, i have to press F5 in browser so it loads the app again. |
|
@danroth27 I think @agonzalezm issue might be related to VS recompiling the app on changes? @agonzalezm Are you using server-side blazor with an HTML file? @danroth27 I'm not very familiar with how the recompilation stuff works in VS and @SteveSandersonMS is out. I think all these issues are related to the server restarting for some reason. Will you be ok, if the output of this item is to change the reconnection UI to handle the case where the circuit is gone and display a different message, like your session was terminated, refresh the page (with a button to trigger a refresh). |
|
@javiercn yes the issue is while recompiling the app on changes that browser doesnt wait till it is recompiled to refresh. I mean modify html code in .razor file, not .html file. |
|
@agonzalezm the behavior you're experiencing is expected. Changes to It seems there is no other work pending on this issue, as the only pending work is being tracked in above referenced issues. |
|
Why is this closed? I'm running this with the latest version on Blazor and the app is hosted via IIs. If I keep my tab open for a few hours the app gives me an "not connected" error. This is with a release build for production. This is really not something that can be shown regularly to users in production. A solution I would prefer: can I detect if the connnection was closed on the frontend with Javascript and force a page reload if the reconnect fails 3 times and say, the user didn't try to reconnect himself? |
|
Hi @edgolub, This issue is closed because there is no known Blazor work tracked here. Blazor Server apps will go into a "not connected" state if the connection is lost for any reason, including the network connection being dropped or the server being restarted. If the server is restarted then there is no way for the app to reconnect back to the same state because the server state is gone. The only way forward is to refresh the browser. Blazor won't refresh the browser automatically, but you can setup your app to do so. For example you could add the following script to your _Host.cshtml file: <script>
// Wait until a 'reload' button appears
new MutationObserver((mutations, observer) => {
if (document.querySelector('#components-reconnect-modal h5 a')) {
// Now every 10 seconds, see if the server appears to be back, and if so, reload
async function attemptReload() {
await fetch(''); // Check the server really is back
location.reload();
}
observer.disconnect();
attemptReload();
setInterval(attemptReload, 10000);
}
}).observe(document.body, { childList: true, subtree: true });
</script>This uses the JS DOM mutation observer API to detect when we’re offering a “reload” button, and automatically does a reload in that case. It has to be careful not to reload before the server actually comes back, otherwise the kiosk would get stuck displaying a “network error” type screen. There is still the potential that the refresh will fail, and if it does then there's no way to retry without user intervention. |
|
Daniel (@danroth27), thank You for the code to autorefresh browser. |
If you sure you want to reload every change,
put it right before:
|
ghost
locked as resolved and limited conversation to collaborators
Describe the bug
When running a server-side blazor project, after some time, the SignalR connection is lost and the following overlay is displayed ("Failed to reconnect to the server"):
However, clicking the retry button does not work - the overlay is still present although the following is logged in the dev tools:
Probably #8710 will fix this, but is there a workaround for preview 5? Also note that there times which an overlay with "Attempting to reconnect to the server" is displayed and this actually reconnects successfully. However, if the app gets to a state in which the "Failed to reconnect to the server" message is displayed, it will not reconnect from the "Retry" button.
To Reproduce
results in the ""Attempting to reconnect to the server", which succeeds though.
Expected behavior
The retry button works.
Additional context
dotnet --info
The text was updated successfully, but these errors were encountered: