Chrome is locking up on everyone behind PFSense
-
I'm using 2.0.3-RELEASE (amd64) built on Fri Apr 12 10:27:56 EDT 2013 FreeBSD 8.1-RELEASE-p13. Everyone that's using Chrome keeps crashing and it forces you to kill the application from Task Manager and to restart it. If you use IE or Firefox its does not happen and you can continue browsing without any difficulties. Are there any known issues between Chrome behind a PFSense that's performing NAT?
- David Thompson
-
Using Chrome happily on loads of boxes behind pfS… Anyway, Chrome lockups and crashes obviously need to reported to Chrome upstream, not here.
-
Using Chrome happily on loads of boxes behind pfS… Anyway, Chrome lockups and crashes obviously need to reported to Chrome upstream, not here.
Yes but IE and Firefox do not exhibit this behavior which I find strange.
-
Using Chrome happily on loads of boxes behind pfS… Anyway, Chrome lockups and crashes obviously need to reported to Chrome upstream, not here.
Agree… have a hard time envisioning how this could be a pfSense issue.
-
I don't fully understand why but if you have some stale default gateways still configured the PFSense was apparently making the decision to send the request out to these causing the weird timeouts. Is this a bug within PFSense that's well known?
- David Thompson
-
I'm using Chrome in one window and Firefox in another and no complaints.
The last time I used IE for anything the USA still had a manufacturing base… So, can't speak to IE.
-
Chrome and Chromium work here (Windows, FreeBSD, Ubuntu) without issue, and I haven't seen complaints from any customers about it.
Not likely to be a general pfSense issue, but I suppose it could be a config issue or an issue with your ISP somehow. (Proxy perhaps? Something else interfering with its traffic?)
