In my case, if I had the command --ignore-certificate-errors, the browser tell me that it's an unsupported command-line.
If I replace the command with --force-fieldtrials, the browser give me the access to Google sites. Strange...
Issues since updating to 56.0.2950.0
Re: Issues since updating to 56.0.2950.0
Yes and yes. Did not help. i also used ccleaner and revo uninstaller pro. Still encountered the same issues with the latest portable version.SRWare wrote:To the ones who have the error:
Have you tried to delete cache etc? Or tried with a clean portable for test?
Previous version is working fine even after restoring settings from backup of latest version.
Re: Issues since updating to 56.0.2950.0
I'm also having same issues on Windows 7 64-bit. Cannot access any google domain without getting ERR_SSL_PROTOCOL_ERROR. Sometime you get ERR_QUIC_PROTOCOL_ERROR. I tried disabling QUIC. Same result. Did not have these issues on macOS.
Re: Issues since updating to 56.0.2950.0
Possible solution:
http://www.srware.net/forum/viewtopic.p ... 887#p33886
http://www.srware.net/forum/viewtopic.p ... 887#p33886
Iron-Updates via Twitter: http://twitter.com/srware
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
Re: Issues since updating to 56.0.2950.0
Having the same problems with Youtube on Win10 64-bit, brand new laptop (1 week old). FF plays Youtube fine. No problem with Google search in Iron.
Re: Issues since updating to 56.0.2950.0
We have fixed this officially in 56.0.2950.1. 32-Bit is already online (just redownload .exe or zip), 64-Bit will come soon (i think tomorrow)
Iron-Updates via Twitter: http://twitter.com/srware
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
Re: Issues since updating to 56.0.2950.0
Thanks!SRWare wrote:We have fixed this officially in 56.0.2950.1. 32-Bit is already online (just re-download .exe or zip), 64-Bit will come soon (i think tomorrow)
I see this workaround (http://www.srware.net/forum/viewtopic.p ... =10#p33886)was suggested before the official fix was released.
Please share what was done to fix this in the latest version.
-
- Posts: 25
- Joined: Tue Nov 29, 2016 12:57 pm
Re: Issues since updating to 56.0.2950.0
Any chance of a fix for this in the 32-bit Linux version of 56.0.2950.0?
Exact same problem; no connection to any Google sites, with a warning that 'Hackers may be trying to steal your passwords and/or identity on this site', etc, etc.
64-bit version works fine; there, the problem doesn't seem to exist.
Any ideas? I've tried all the usual stuff; clearing cache, etc, and it doesn't seem to have any effect.
Mike.
Exact same problem; no connection to any Google sites, with a warning that 'Hackers may be trying to steal your passwords and/or identity on this site', etc, etc.
64-bit version works fine; there, the problem doesn't seem to exist.
Any ideas? I've tried all the usual stuff; clearing cache, etc, and it doesn't seem to have any effect.
Mike.
Re: Issues since updating to 56.0.2950.0
will be fixed with the upcoming 57Mike_Walsh wrote:Any chance of a fix for this in the 32-bit Linux version of 56.0.2950.0?
Exact same problem; no connection to any Google sites, with a warning that 'Hackers may be trying to steal your passwords and/or identity on this site', etc, etc.
64-bit version works fine; there, the problem doesn't seem to exist.
Any ideas? I've tried all the usual stuff; clearing cache, etc, and it doesn't seem to have any effect.
Mike.
Iron-Updates via Twitter: http://twitter.com/srware
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
Donations via Paypal and Bitcoin:
http://iron-start.com/spenden.php
-
- Posts: 25
- Joined: Tue Nov 29, 2016 12:57 pm
Re: Issues since updating to 56.0.2950.0
Jolly good. Thanks for that.
Will look forward to it. Chrome on 64-bit is not giving any trouble; I'm currently 'beta'-testing Chrome 58, and, as previously stated, it behaves itself. So does the 64-bit version of Iron.....it's just the 32-bit version that is misbehaving at the moment!
It's just a wee bit annoying on what is otherwise a very fine browser. I'm beginning to suspect that the guys at the Chromium Project decided to try out a couple of new things in this last release or two. I rather think it's possibly related to this new certificate authority Google are in the process of setting up, since it's set by default to automatically distrust any certificate that isn't signed by their new procedure.
Mike.
Will look forward to it. Chrome on 64-bit is not giving any trouble; I'm currently 'beta'-testing Chrome 58, and, as previously stated, it behaves itself. So does the 64-bit version of Iron.....it's just the 32-bit version that is misbehaving at the moment!
It's just a wee bit annoying on what is otherwise a very fine browser. I'm beginning to suspect that the guys at the Chromium Project decided to try out a couple of new things in this last release or two. I rather think it's possibly related to this new certificate authority Google are in the process of setting up, since it's set by default to automatically distrust any certificate that isn't signed by their new procedure.
Mike.