[SOLVED] ERR_CONNECTION_RESET After upgrading to 19.1

Started by logo2002, January 31, 2019, 10:56:57 PM

Previous topic - Next topic
January 31, 2019, 10:56:57 PM Last Edit: February 02, 2019, 04:04:17 PM by logo2002
Hello guys,

I did the upgrade to the latest version 19.1 on my Opnsense firewall at home but since that upgrade I noticed that I got lot of ERR_CONNECTION_RESET in my web browser.

I thought it was an issue with the website/DNS or other but Ping command to these sites are OK and the DNS server is working fine to (8.8.8.8).

Do you have any idea of what can be the root cause of this issue since the configuration stays the same ?

Thank you,
Logan


February 01, 2019, 08:04:23 AM #2 Last Edit: February 01, 2019, 08:06:11 AM by tiki1980
Same problem here, this is what i tried, unfortunately had to revert back to the previous release. I just did an upgrade through the gui, no clean install

This is my config

  • bridged lan interfaces
  • opendns nameservers configured
  • bind for blocklist
  • unbound in forwarding mode.
This did not work from lan disconnects and slowness all around. I reverted to the unmasq dns but this also did not help. Changed dns servers to google dns but also did not help. Did revert to my backup of the previous release and all is working well

If wanted i can share my config file with the dev's

February 01, 2019, 08:16:40 AM #3 Last Edit: February 01, 2019, 08:32:45 AM by scrensen
Same issue here

Also I see blocked localhost traffic in the firewall log, that i never saw before the upgrade. And some blocked VLAN traffic

I can share logs if needed

scrensen and tiki1980, please open new threads as they are different.

logo2002 do you use proxy? Does telnet to the fqdn with port 80 or 443 work?

Hi Mimugmail,

I am not using any proxy and I already check if some of them were activated after the upgrade.

Ping to the hostname/IP is ok.
Nslookup of the hostname is ok.
Telnet to port 443 of the host is ok.

It seems that something in the firewall is stopping the connection to force the connection state to stop/reset.

I tried to restore the backup done before the upgrade when everything was working well but it doesn't change anything to my issue.

Nothing is blocked by the firewall rules (checked in the logs).

Thank you for your help.

Regards,
Logan

No I have the same issue

Strangely enough a curl from my MacBook commandline works just fine. But via three different browsers I have this issue.

And literally happened directly after the upgrade. Before that all was fine.

And when I connect my laptop directly to my cable modem it also works perfectly fine. I can not think of any other reason then the 19.1 upgrade

I made some traffic captures and at first glance I see a tcp window update and after that many TCP retransmissions.

Where as the successful session via curl just shows the 'normal behaviour'

Quote from: scrensen on February 01, 2019, 09:11:14 AM
No I have the same issue

Strangely enough a curl from my MacBook commandline works just fine. But via three different browsers I have this issue.

And literally happened directly after the upgrade. Before that all was fine.

And when I connect my laptop directly to my cable modem it also works perfectly fine. I can not think of any other reason then the 19.1 upgrade

I made some traffic captures and at first glance I see a tcp window update and after that many TCP retransmissions.

Where as the successful session via curl just shows the 'normal behaviour'

Interfaces : LAN : MSS

Set to 1400 and test again ...

Shouldn't be the issue, just curious

Thanks for the response

Didn't change anything.

Another thing to make it even more strange. I tried google.nl like 5 times in Safari and no go. While curl works just fine.

The tried Firefox again and it work for about three times. And then it stopped working. Same error.

As said, DNS works fine all the time. Could it have to do with some TCP buffers or something similar?

Same here, and I can't rollback because it says "failed, no signature found"
Someone know how to do it?

@All: experienced the same. Clear Chrome browsing history (assuming you use chrome) solved my issue.

https://www.webnots.com/how-to-fix-err_connection_reset-error-in-google-chrome/


@Northguy

I have this issue on all of my devices.

- Google Home
- Windows PC
- MAC laptop
- Playstation 4

Some website are available and some not.