What would cause FireFox to crash with a signature of RtlpWorkerCallout, crash reason = EXCEPTION_ACCESS_VIOLATION? I'm trying to figure out what feature or plugin would be involved.
The same problem seems to be causing trouble with IE, but not with Chrome.
It turned out to be a conflict with the Firewall portion of Trend Micro Antivirus. I didn't find a workaround. I switched to a different antivirus program.
Related
I can not get localhost to work on chrome after upgrading to macOS Catalina. I spent a lot of time trying to figure out why I was getting this message
localhost normally uses encryption to protect your information. When Google Chrome tried to connect to localhost this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be localhost, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.
You cannot visit localhost right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
(I wish I had taken a screen shot)
I don't know if this is the "best" solution but it got me able to code again so I figured I would share. I was seriously stuck and couldn't find any answers and saw someone mention this solution to another issue. Go to chrome://flags/#allow-insecure-localhost and change to enable.
Hope this helps someone else. I know this isn't really a question but there's not really a way to just share this. I guess I could use twitter and reddit.
OS X Catalina increased the requirements for an SSL/TLS certificate to be acceptable around November 2019. Notably, certificates now need a "Subject Alternative Name" section, which was not previously required. Note that this is an OS-level requirement and not specific to a single browser (although it doesn't affect FireFox because Firefox doesn't use the OS security stack).
The solution to your issue is how you generate the SSL certificate, not anything you can do as a Chrome user. This particular issue can not be bypassed by clicking through a Chrome warning message.
Also note that fixing this issue for OS X may make the certificate unusable on Chrome + Linux (I have linked to WebPack Dev Server's GitHub Issue discussion of this issue).
I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.
Every attempt to connect to Wired.com is met with a certificate error.
I've checked the usual suspects and even done things that probably have nothing to do with it.
Browsers tried
Safari=failed
Chrome=failed
Brave=failed
Firefox=success
Verified no Chrome extensions interfering (incognito w/ no approved incog extensions)
Same with Safari.
Flushed DNS
Rebooted
Time settings obv correct
I started to get paranoid thinking that something is hijacking my connection, but the only active ports I've got open and connected are... well, supposed to be open. And then the fact that it works with Firefox is even stranger. Firefox is my proxy browser, but it works via proxy w/out.
This is a recently upgraded Sierra machine. I'm not an avid wired reader, so I couldn't tell you if it was happening previously, but I can say I've got 4 other mac test machines here and none of them are experiencing the same issue.
Sierra vs Capitan doesn't make a difference. And this is now going on a 2 week issue. Wired appears to be literally the only site effected. At this point it's more a curiosity at getting to the bottom of this than anything else, since it does appear to be something isolated to this machine.
Also, I think we can rule out a CDN issue. As all my other machines are connecting from this same wanIP.
Man, just absolutely any suggestions for more internals I could go digging through to try and get to the bottom of this would be oh so greatly appreciated. Because I've about relegated myself to keyboard head smashing.
The problem (most likely) is caused due to recent issue at GlobalSign as they incorrectly revoked their cross-certificates. Full statament from GlobalSign: Certificate Revocation Issue
Thanks guys. That GlobalSign certificate was cached.
Removing the cache at
/var/db/crls worked
I backed it up first just in case, but sudo wiping the cache didn't cause any problems.
sudo rm /var/db/crls/crlcache*
sudo rm /var/db/crls/ocspcache.db*
There is something weird happening on the website of the company I'm working for.
On both Firefox and Firebug console log, I get an unknown network error.
There is no code reference for the error, and I can't track it on other browsers.
However, it's there, and I don't know how to solve it, nor what it is.
Other sites with the same theme, same domain registrar and on the same server work just fine, showing no problems at all.
What the heck is that??
It seems that the latest update of Contact Form 7 Plug-in solved the problem!
I have run into a few cases where IE10, with Document and Browser Modes set to IE8, is unable to reproduce bugs observed in a genuine copy of IE8 on a co-worker's computer. For most IE version-specific problems, switching IE10 to IE8 mode allows me to recreate them just fine, but more than once I've had version-specific problems that only genuine IE8 can reproduce.
Is there any reasonably easy way to get IE8 on my computer without losing my IE10 installation?
(A "No" answer is better than a convoluted solution)
A "No" answer is better than a convoluted solution
Well, in that case, a "No" answer is what you shall get.
No. You can't.
Just for completeness, the "convoluted" solution:
Use a VM (Virtual Machine). This is the standard solution for testing with old IE versions.
You can download pre-configured VMs for testing every IE version from Microsoft's site http://modern.ie/
Alternatively, you might want to try out http://browserstack.com/, which is an online VM provider; same VMs as you can get from modern.ie, but running on their servers via your browser, rather than running it yourself on your own hardware. It's a paid service, but extremely convenient (oh, and you can get a free 3 month subscription from modern.ie)