Webmail auto refresh issue on SmarterMail 17

Problem reported by rishikesh Somshetti - 10/29/2020 at 3:30 AM

Resolved

We have many user complaints stating that the webmail auto refresh is not working properly after upgrade to SmarterMail 17. Restarting or recycling the application pool temporarily solves this issue but after some time it stops working again.

In the browser console tab we observed these errors

[SignalR Self Check] Sent request to server waiting response...
site-v-100.0.7593.31139.8d8710042591c00.js:396 Linking touchContext
o @ site-v-100.0.7593.31139.8d8710042591c00.js:396
site-v-100.0.7593.31139.8d8710042591c00.js:99 [SignalR Self Check] Server did not respond within 30000ms, check FAILED.
angular-v-100.0.7593.31139.8d8710042591c00.js:15638 Possibly unhandled rejection: undefined
(anonymous) @ angular-v-100.0.7593.31139.8d8710042591c00.js:15638
DevTools failed to load SourceMap: Could not load content for https://webmail.example.com/interface/output/angular.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Is there anything we can do to fix this issue permanently?

12 Replies

Reply to Thread

Gabriele Maoret - SERSIS Replied

10/29/2020 at 3:51 AM

Same here, but this issue is started since SmarterMail 16... Never resolved

Gabriele Maoret - Head of SysAdmins at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)

Employee Replied

10/29/2020 at 7:47 AM

Employee Post

We have a task to thoroughly investigate the SignalR issues after the next public build release.

rishikesh Somshetti Replied

11/4/2020 at 3:07 AM

Is there any timeline when this will be resolved? This function is very important for us.

John C. Reid Replied

1/13/2021 at 8:46 AM

It is 1/13/2021, we are running SM 17 Public Release 7669, and our users are still reporting this problem.

John C. Reid / Technology Director John@prime42.net / (530) 691-0042 1300 West Street, Suite 206, Redding, CA 96001

Gabriele Maoret - SERSIS Replied

1/14/2021 at 3:27 AM

Vincent Sammons Replied

1/16/2021 at 11:50 AM

This is a big problem since we upgraded... When will this be fixed, or what version can we downgrade to safely?

Vincent Sammons

John C. Reid Replied

1/18/2021 at 8:15 AM

In case this helps anyone else. In my case we had two sites and applications pools in IIS. The one created by the install named "SmarterMail" and the one we were using that has the servers hostname. This was causing the SignalR to get confused. Once I made sure that all the bindings that were on our hostname site I deleted the site and application pool for SmarterMail. This appears to have fixed this issue for us.

John C. Reid / Technology Director John@prime42.net / (530) 691-0042 1300 West Street, Suite 206, Redding, CA 96001

Vincent Sammons Replied

1/18/2021 at 8:55 AM

I believe I am having similar SignalR issue. I am using the default Smartermail and no other. I did have the Port 80 being redirected from another site to the smartermail site. But I since removed it from the bindings of the redirect sites and added it to smartermail. I am still having this issue.

Vincent Sammons

John C. Reid Replied

1/18/2021 at 9:50 AM

You seem to have port 443 bound twice. You should pick one. Do you want that site to respond to all requests, on all IPs, on port 443? Do you want that site to only respond when the host headers equal your UNC of secure.vssbus....... on all IPs on port 443? You need one or the other, not both.

John C. Reid / Technology Director John@prime42.net / (530) 691-0042 1300 West Street, Suite 206, Redding, CA 96001

Vincent Sammons Replied

1/18/2021 at 10:05 AM

I added this after the fact as a catch all to capture all unclaimed 443 port traffic. It had no effect on my issue one way or the other.

Vincent Sammons

John C. Reid Replied

1/18/2021 at 11:16 AM

I suggest you create a ticket.

John C. Reid / Technology Director John@prime42.net / (530) 691-0042 1300 West Street, Suite 206, Redding, CA 96001

JerseyConnect Team Replied

6/22/2021 at 11:52 AM

We just had a report of this issue with webmail not auto refreshing this morning. I found this thread before opening a ticket and sure enough the SignalR error was present in the browser console. I then noticed that the binding for port 80 was hard set to one of the server's IPs. I changed it to "All Unassigned" and the SignalR error stopped.

Back to Community Threads

Please leave this box unchecked

12 Replies

Reply to Thread

Tags

Related Knowledge Base Articles