#StackBounty: #google-chrome #scheduled-tasks #windows-task-scheduler #python3 #selenium Task Scheduler does not launch chrome when Run…

Bounty: 50

I have Python script for web-scraping. I am running it using papermill and then I created a batch file that I use on task scheduler to run. This workflow was running fine until my virtual machine got updated. I am able to successfully run it manually or "Run only when user is logged on" without any error.

When the option Run whether user is logged on or not is selected, It just hangs at a step where it needs to open a browser to log in and then after 20-30 mintutes, It gives me time-out session error as below:

SessionNotCreatedException: Message: session not created
from timeout: Timed out receiving message from renderer: 600.000
  (Session info: chrome=93.0.4577.82)

Things I have tried:

  • I have checked the box "Run with Highest Privileges"
  • I have checked the version of chrome version and everything is up-to-date
  • Start in option is added already
  • Start only if the network connection is available has "Any Connection"
  • Trigger has the Enabled option checked

This is how my .bat file looks like:

@echo off
SET LOGFILE=C:pathlogslog-%date%.txt
echo on
call :logit >>%LOGFILE%
exit /b 0 

:logit 
echo "Activate the anaconda prompt for the remaining commands."
echo "Note that the ProgramData folder is a hidden item."
call C:pathScriptsactivate.bat

echo "Change directory at anaconda prompt to application location."
cd C:path

echo "Run the Python application"
python papermill.py 


echo "Use taskkill to end the geckodriver.exe task."
taskkill /im geckodriver.exe /f

exit
echo "Close the command prompt."

@timeout 6 >nul

Please suggest as I have tried


Get this bounty!!!

#StackBounty: #windows-10 #google-chrome #keyboard-shortcuts Shortcut for Focusing Console Filter in Chrome

Bounty: 50

I’m frequently needing to filter out my Chrome console during web development. Unfortunately every time I want to filter for a different term, I must manually click the search box. I don’t see anything about a shortcut for focusing the filter bar in the Chrome devtools shortcut docs, is there a way to assign a shortcut to do this? This would make using the filter much master.

If there’s an extension that will do it I’m also open to that.

OS: Windows 10

enter image description here


Get this bounty!!!

#StackBounty: #google-chrome #keyboard-shortcuts Shortcut for Focusing Console Filter in Chrome

Bounty: 50

I’m frequently needing to filter out my Chrome console during web development. Unfortunately every time I want to filter for a different term, I must manually click the search box. I don’t see anything about a shortcut for focusing the filter bar in the Chrome devtools shortcut docs, is there a way to assign a shortcut to do this? This would make using the filter much master.

If there’s an extension that will do it I’m also open to that.

OS: Windows 10

enter image description here


Get this bounty!!!

#StackBounty: #google-chrome #puppeteer #headless #google-chrome-headless #screen-capture Google Chrome Headless Error "Not suppor…

Bounty: 250

I am using Puppeteer latest version with Chromium 80 and I’m trying to record video from page in chrome headless and turned on all these flags:

{
  headless: true,
  devtools: false,
  args: [
    '--no-sandbox',
    '--allow-insecure-localhost',
    '--enable-usermedia-screen-capturing',
    '--use-fake-ui-for-media-stream', // In headless: false it will capture display rather than tab and in headless: true doesn't work
    '--auto-select-desktop-capture-source=[RECORD]', //[RECORD] is the title of my localhost page trying to screen capture
    '--remote-debugging-port=9222',
    '--window-size=1440,900',
  ],
  ignoreDefaultArgs: [
    '--mute-audio',
    '--disable-media-session-api',
  ]
}

On windows if this is headless : false it will capture the chrome tab (sometimes crashes). But if this is headless : true even on Windows it says it is Not supported.
If --use-fake-ui-for-media-stream flag is on then it is another story and it will capture one of my displays regardless of being headless true or false.

Now I want to use this on my linux server where there is no display and I just want the chrome headless : true to capture my chrome tab. I know it can do that because I can see the screen in headless : true mode in the DevTools. If it is creating a display on DevTools it MUST be able to create the display on screen capture. I suppose there must be other flags to be turned on on Puppeteer so it is allowed to do so. I am using navigator.mediaDevices.getDisplayMedia in order to get the screen data.

I also have tried this video configuration and it didn’t work (crashed) and apparently only works on extensions and I need to get source id from background:

screenStream = await navigator.mediaDevices.getDisplayMedia({
        video: {
            //mandatory: {
            //    chromeMediaSource: 'tab', // Not using this!
            //}
        },
        audio: false
});

Is there anyone that knows what flags should be also considered into the Puppeteer?

Please Note that I don’t want to use xvfb and Selenium (WebDrive) or any extensions in my chrome headless.


Get this bounty!!!

#StackBounty: #angular #google-chrome #visual-studio-code #progressive-web-apps #vscode-debugger Unbound breakpoint – Angular, VS Code,…

Bounty: 50

Versions:

Angular CLI: 11.2.11
Node: 14.16.0
VS Code: 1.59.0
Chrome: 92.0.4515.131 
Debugger for Chrome (Nightly): v2020.2.15300
JavaScript Debugger (Nightly): v2021.8.217
(No other VS Code extensions loaded)

Environment

Windows 10 – Running as limited user. Not able to install anything but approved software, meaning, I’m stuck with the version of Node above, I can upgrade VS Code, but not install a specific version, etc.

launch.json:

    {
        "name": "Launch PWA-Chrome",
        "request": "launch",
        "type": "pwa-chrome",
        "url": "http://localhost:4200/",
        "webRoot": "${workspaceFolder}"
    },
    {
        "name": "Attach to Chrome",
        "port": 9222,
        "request": "attach",
        "type": "pwa-chrome",
        "webRoot": "${workspaceFolder}"
    }

Details:

  • Occurs for a vanilla Angular app configured as a PWA. Set a
    breakpoint anywhere and get "unbound breakpoint".
  • Occurs when
    launching Chrome and when attaching to Chrome (in debug mode).
  • Does not occur for non-PWA vanilla angular app – I can debug non-PWA vanilla angular app.

Research and what I’ve tried:

  • My situation is different than this: Unbound breakpoint – VS Code | Chrome | Angular . Mine is a PWA and I always have an unbound breakpoint when starting with "ng serve".
  • Tried change in angular.json: "sourceMap": true – No effect
  • Tried "Run -> Disable All Breakpoints, then Enable All Breakpoints" – No effect
  • Tried downgrading VS Code to 1.52.1 (when debugging last worked) – No effect
  • Tried adding to webpack: devtoolModuleFilenameTemplate: ‘[absolute-resource-path]’ – No effect
  • Tried disabling all extensions, except for Chrome and JS debugger – No effect
  • Tried attaching to Chrome in debug mode – still won’t hit a breakpoint


Get this bounty!!!

#StackBounty: #windows-10 #google-chrome #firefox Is there any way to reduce more than the minimum width that browsers allow?

Bounty: 100

Operation System: Windows 10
Screen resolution: 1366×768

I’m trying to make the browsers even smaller in width, but they won’t let me pull more to the side than this amount below, Google Chrome on the left and Firefox on the right. Is there any way to remove this block and lessen more than that?

Note: My problem is screen space on my monitor, so I needed to be able to shrink a little more the browser’s.

The idea is to increase this black space between browsers and have more freedom to adjust the width without blocking the minimum.

enter image description here


Get this bounty!!!

#StackBounty: #google-chrome #security #google-chrome-extensions #chromium Chrome uses Preferences and Secure Preferences to manage ext…

Bounty: 100

I found this post: What is the difference between Preference and Secure Preference file in Google Chrome?

But I want to know further: When does Chrome decides to use Secure Preferences and when to use Preferences file for maintaining extensions?

Because I found that in my computer the newly installed extension’s manifest.json file’s whole content is copied to Preferences file. Which means Chrome uses Preferences file to maintain my extensions. In this case, my Secure Preferences file has only one line as below:

{"protection":{"super_mac":"abc123xxxxxxx"}}

While in my colleague’s computer the installed extension’s manifest.json file’s content is not copied to Perefences file, but it is copied to Secure Preferences file. Which means Chrome uses Secure Preferences file to maintain his extensions.

Why? What is the factor for Chrome to decide to use Preferences file or Secure Preferences file for maintaining the extensions?


Get this bounty!!!

#StackBounty: #windows-10 #networking #google-chrome #dns Chrome and Spotify app can't connect

Bounty: 300

I’m having this really weird problem on my computer that I can’t seem to wrap my head around. Occasionally (and almost always after a reboot), the spotify app can’t seem to connect to it’s servers. When this happens, Chrome is also affected, and it affects all known websites related to Spotify (their web page, web player, their community etc, basically all of *.spotify.com).

This is what it looks like, note the empty remote address column, which makes me suspect a DNS problem.

network tab of Chrome

Now, after a while, this seems to "fix" itself, but it takes like 5-10 minutes or so. Meanwhile, Brave browser (which is basically chrome in disguise) works fine, so does Invoke-WebRequest from powershell. Running ipconfig /flushdns and restarting Chrome does nothing.

I do know that the Spotify app does use the Chrome engine under the hood, but I would expect it to run it’s own bundled engine, and not my installed Chrome? So why do they affect each other? Also, when this problem stops, it seems to stop simultaneously for both apps.

One suspicion I had, was that it is IPv6 that is buggering me. Spotify actually resolves IPv6 addresses, and I don’t have IPv6. However, I did disable IPv6 on my Wi-Fi adapter, but to no avail.

I’ve also verified that Chrome and Spotify are both allowed through windows firewall.

I’m kind of stuck in my troubleshooting, and some new ideas would be welcome. Also, Spotify is the only known service that seems to have this problem, which is also strange.

EDIT: I’ve noticed that this affects some more sites. plex.tv, as well as the Netflix app, suffer from the same problem. When I can’t visit these sites, other sites are fine, like github.com, google.com, AWS console etc.

I’m stumped. I’ve managed to start the debug logger in Chrome, and when requesting a url that fails, I get this:

[15564:26264:0704/214452.685:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://plex.tv/
[33512:27416:0704/214452.735:INFO:cpu_info.cc(53)] Available number of cores: 8
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.622:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.626:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.627:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING

The 192.168.0.148 is a Chromecast on my network, and those errors might be irrelevant, but the error line is interesting:

[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101

I don’t understand why I would get SSL error in multiple applications, which after awhile just goes away. Also, why does it only affect some applications, and not all? (Brave, for instance)


Get this bounty!!!

#StackBounty: #windows-10 #networking #google-chrome #dns Chrome and Spotify app can't connect

Bounty: 300

I’m having this really weird problem on my computer that I can’t seem to wrap my head around. Occasionally (and almost always after a reboot), the spotify app can’t seem to connect to it’s servers. When this happens, Chrome is also affected, and it affects all known websites related to Spotify (their web page, web player, their community etc, basically all of *.spotify.com).

This is what it looks like, note the empty remote address column, which makes me suspect a DNS problem.

network tab of Chrome

Now, after a while, this seems to "fix" itself, but it takes like 5-10 minutes or so. Meanwhile, Brave browser (which is basically chrome in disguise) works fine, so does Invoke-WebRequest from powershell. Running ipconfig /flushdns and restarting Chrome does nothing.

I do know that the Spotify app does use the Chrome engine udner the hood, but I would expect it to run it’s own bundled engine, and not my installed Chrome? So why do they affect eachother? Also, when this problem stops, it seems to stop simultaneously for both apps.

One suspicion I had, was that it is IPv6 that is buggering me. Spotify actually resolves IPv6 addresses, and I don’t have IPv6. However, I did disable IPv6 on my wifi adapter, but to no avail.

I’ve also verified that Chrome and spotify are both allowed through windows firewall.

I’m kind of stuck in my troubleshooting, and some new ideas would be welcome. Also, Spotify is the only known service that seems to have this problem, which is also strange.

EDIT: I’ve noticed that this affects some more sites. plex.tv, as well as the Netflix app, suffer from the same problem. When I can’t visit these sites, other sites are fine, like github.com, google.com, AWS console etc.

I’m stumped. I’ve managed to start the debug logger in Chrome, and when requesting a url that fails, I get this:

[15564:26264:0704/214452.685:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://plex.tv/
[33512:27416:0704/214452.735:INFO:cpu_info.cc(53)] Available number of cores: 8
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.622:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.626:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.627:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING

The 192.168.0.148 is a Chromecast on my network, and those errors might be unrelevant, but the error line is interesting:

[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101

I don’t understand why I would get SSL error in multiple applications, which after a while just goes away. Also, why does it only affect some applications, and not all? (Brave, for instance)


Get this bounty!!!

#StackBounty: #windows-10 #networking #google-chrome #dns Chrome and Spotify app can't connect

Bounty: 300

I’m having this really weird problem on my computer that I can’t seem to wrap my head around. Occasionally (and almost always after a reboot), the spotify app can’t seem to connect to it’s servers. When this happens, Chrome is also affected, and it affects all known websites related to Spotify (their web page, web player, their community etc, basically all of *.spotify.com).

This is what it looks like, note the empty remote address column, which makes me suspect a DNS problem.

network tab of Chrome

Now, after a while, this seems to "fix" itself, but it takes like 5-10 minutes or so. Meanwhile, Brave browser (which is basically chrome in disguise) works fine, so does Invoke-WebRequest from powershell. Running ipconfig /flushdns and restarting Chrome does nothing.

I do know that the Spotify app does use the Chrome engine udner the hood, but I would expect it to run it’s own bundled engine, and not my installed Chrome? So why do they affect eachother? Also, when this problem stops, it seems to stop simultaneously for both apps.

One suspicion I had, was that it is IPv6 that is buggering me. Spotify actually resolves IPv6 addresses, and I don’t have IPv6. However, I did disable IPv6 on my wifi adapter, but to no avail.

I’ve also verified that Chrome and spotify are both allowed through windows firewall.

I’m kind of stuck in my troubleshooting, and some new ideas would be welcome. Also, Spotify is the only known service that seems to have this problem, which is also strange.

EDIT: I’ve noticed that this affects some more sites. plex.tv, as well as the Netflix app, suffer from the same problem. When I can’t visit these sites, other sites are fine, like github.com, google.com, AWS console etc.

I’m stumped. I’ve managed to start the debug logger in Chrome, and when requesting a url that fails, I get this:

[15564:26264:0704/214452.685:VERBOSE1:network_delegate.cc(32)] NetworkDelegate::NotifyBeforeURLRequest: https://plex.tv/
[33512:27416:0704/214452.735:INFO:cpu_info.cc(53)] Available number of cores: 8
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.563:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.607:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.622:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(220)] [192.168.0.148:8009, auth=SSL_VERIFIED] Connect readyState = ReadyState::NONE
[9692:25292:0704/214454.622:VERBOSE1:cast_socket.cc(379)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnect
[9692:25292:0704/214454.626:VERBOSE1:cast_socket.cc(393)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoTcpConnectComplete: 0
[9692:25292:0704/214454.627:VERBOSE1:cast_socket.cc(410)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnect
[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(433)] [192.168.0.148:8009, auth=SSL_VERIFIED] DoSslConnectComplete: -101
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(653)] [192.168.0.148:8009, auth=SSL_VERIFIED] SetErrorState ChannelError::AUTHENTICATION_ERROR
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(575)] DoConnectCallback (error_state = ChannelError::AUTHENTICATION_ERROR)
[9692:25292:0704/214454.633:VERBOSE1:cast_socket.cc(615)] [192.168.0.148:8009, auth=SSL_VERIFIED] Close ReadyState = ReadyState::CONNECTING

The 192.168.0.148 is a Chromecast on my network, and those errors might be unrelevant, but the error line is interesting:

[15564:26264:0704/214454.632:ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -101

I don’t understand why I would get SSL error in multiple applications, which after a while just goes away. Also, why does it only affect some applications, and not all? (Brave, for instance)


Get this bounty!!!