New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Remote Host Closed the Connection Exception #5521
Comments
The 0x80070057 error code means that Windows ran into a storage issue. Can you look at your system volume and report back:
Looking at the caching strategy there are some optimizations that could be made to reduce the number of files produced. |
Other recommendations from Google:
From: https://www.lifewire.com/fix-error-code-0x80070057-4691502 |
The time on my Azure VM currently looks correct. |
|
Quick update: Exceptions continue to occur after chkdsk was run |
We're experiencing the same issue with GetAvatar.ashx, exactly as shown above |
@dataCollegechurch @mikedotmundy What version of IIS are you using? Is it the same for both of you? I noticed that both your stack traces have |
Can you all check your IIS version? If it is IIS7 Microsoft ended support of that in Jan 2020. It sounds like the cached images are not being written (hence the lack of the |
Our stack trace also shows the IIS7 message, but we're running version 10 |
|
@mikedotmundy - I think you can look at the Security Permissions for the folder in question. We are also running IIS10 and our App Pool is running as LocalSystem. I believe LocalSystem shows up as SYSTEM most places. It does have access to create new folders in our case. |
Ok thank you @dataCollegechurch - I wondered if that was it - my permissions look the same. |
Coming here just to report that I'm seeing this on v16.0 alpha (1.16.0.10). The exceptions happen when I visit a person profile (and sometimes the internal homepage) and the URLs in the exceptions point at valid profile images or images with the initials of the person, but not every time, or for every person. I'll note that our Person Image file type is stored on Cloudinary, not on local storage or the db... in case that could be part of the issue. Like others here, we have no /App_Data/Avatar/Cache directory. Only Fonts and Masks are directories there. Running on Win 2022/IIS10 here. |
We are also continuing to see this on Alpha v1.16.0.10. |
We are also using cloudinary, @mikedotmundy @zackdutra , where are you storing your people images? |
Ours are database |
We switched to Azure blob storage, but some are still in database |
Greetings everyone. We've done some extensive research on this one and the advisement is:
That means it's still possible there could be other places in Rock where a "The Remote Host Closed the Connection" exception occurs in the future. So, if it does happen, please feel free to report it with the stack trace and we'll consider handling/ignoring that case. Ultimately we could decide to ignore those exceptions system wide, but we'll get there if we get there. |
Should we open a separate issue to research why the ~\App_Data\Avatar\Cache folder is missing on some instances? |
Anecdotally it appears that this issue is occurring for some churches but not others. If this exception is driven by the client browser dropping the connection, I would expect for this error to be occurring for every church. Personally I would not be comfortable ignoring this error until we could determine either that it is occurring for all churches or why it is only occurring for some. |
Please go through all the tasks below
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
This is possibly related to #4652, but the exception/stack trace is different, so I am opening a new bug. This seems to be some issue with the GetAvatar feature introduced in v15.0.
Since updating to v15.1, (possibly in v15.0 also) we have been regularly seeing the following exception:
Stack Trace:
Expected Behavior
No exception.
Actual Behavior
Exception is logged.
Steps to Reproduce
See above.
I have been unable to figure out exactly what page(s) or action(s) are causing these exceptions to happen, however, it is happening for people who do not have access to our internal Rock pages, which means most likely, it is happening when users are logged into their external account and/or associated pages.
Rock Version
v15.1
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: