Technical Support for Jaksta Media Recorder

Support | Windows | Technical | Jaksta Media Recorder | Unexpected error configuring the HTTPS/SSL monitor for Default LAN

Unexpected error configuring the HTTPS/SSL monitor for Default LAN

Asked by GregC @ 21 Jul 2020 12:07 / Views: 27

I am getting the "Unexpected error configuring the HTTPS/SSL monitor for Default LAN" message.

I have done what you suggested in the couple of support posts about being sure to set it as 'DefaultLAN' but it does not work for me.

Thanks

GC


From @

 Hi,

Thanks for the account activation.

I have attached the logs below.

GregC


From @

The error (0x2F92) is because you can't change the proxy settings on your computer.  A google search indicates that this maybe because:


1.  WinHTTP Web Proxy Auto-Discovery Service is not running or enabled.

2.  A windows update has "broken" the proxy cfg in windows.

Can you change your proxy settings in Internet Explorer?  IE -> Tools (the cog icon) > Internet Options > Connections tab > LAN settings > Advanced?

JMR uses an internal proxy to detected media streamed over HTTPS.  This proxy is switched on when you click AUTO and off when you turn it off.

 


From @

I have looked at this and the WinHTTP Web Proxy Auto-Discovery Service was disabled. So I enabled that via the registry as in image '3' below to 'automatic'. I cant seem to force it to start from boot, just the 'automatic' option. Should I try the 'manual' setting from boot?


The other two images show what I am getting for the IE route you mentioned.

I still cannot change the LAN settings to automatically select the proxy.

When I try to manually start the WinHTTP Web Proxy Auto-Discovery Service via the 'Component Service' I get image 3 below.

If it down to 'associated devices', does anyone know what they are and how to enable them?

Any ideas are greatly received.


From @

Min is set to manual.

image


Perhaps see if there is more info about what is wrong in your windows event log.


From @

Hi,

I have got JMR to run without the error by totally uninstalling it and reinstalling it and the NCAP, and setting WinHTTP to manual.

However, it does not now find any HTTPS feeds.

Could you also give a hint as to where I can find the specific event log.

Thanks.


From @

Please provide debug logs again if the HTTPS monitor is now running without error.


From @

Hi,

I have attached the log. Was trying to record this video off the BBC:

https://www.bbc.co.uk/news/video_and_audio/headlines/53543470/breaching-whale-cheers-devon-fishermen

Thanks.


From @

Your logs dont show you going to that page.  Make sure AUTO is on before you open your browser and go to the page you want to capture from.


From @

Hi,

1. Started Jaksta.

2. Started Firefox.

3. Ran video link.

Nothing shows up in the recording box, no multiple streams box opens as per your image.

image



From @

 I tried again with a different page, same site and I think that should be visible in the logs attached.

Regards.


From @

I tried again today with the same result.

I did notice when I then tried to download it by the "download from the URL" it said that there was a problem with SSL if that explains anything.

At the moment the software is useless to me. I can use OBS studio, but I want to be able to do other stuff in the foreground with sound.

Thanks for any help.

Regards

Greg


From @

Your logs show the stream being detected and a capture starting (which would is appearing in the JMR UI) but show some issue with your settings for preferred download quality and preferred download format.  No stream is selected and the capture stops.

What do you have these set to?

Settings > Internet Downloads


From @

I had it set at 1080p quality. Changed it and it does now offer me a choice - but crucially not on Firefox!?

Why is the "Preferred Download Quality" not an advisory as it implies? I only set it as I thought, if there were a 1080p download on offer, it would choose that one, but if not, it would go for what was on offer?

In the past it just downloaded the stream and didn't give a selection of streams? Did you change that in the later software versions?


From @

Let me have a look as it should be working as you described (it is advisory).  

There are new max resolution settings in that list, from version 7.0.12, intended to give greater control, than just the   Lowest, Median, Highest that were the only options previously.

Please provide debug logs from Firefox if you arnt getting a prompt at all from that browser, or a download that is in error with "No stream selected to download"

https://www.jaksta.com/support/windows/technical/jaksta-media-recorder/how-to-generate-debug-logs-6000009063


From @

 Attached the latest log.

Here was the order of actions:

1. start Jaksta with 'Auto' running.

2. start Firefox to blank page.

3. select bookmark page 'https://www.bbc.co.uk/news/video_and_audio/headlines/53631866/first-spacex-crewed-mission-lands-safely'

4. click 'Play' button.

As you can see from the logs, nothing from Firefox is picked up by Jaksta.


From @

This beta should correct the issue where an available stream was dont being detected when you had a preferred quality set

 

http://downloads.jaksta.com/release/jak7/JMR7/7.0.20.0/JMR7-7.0.20.0.exe

 

Your logs from trying to use Firefox show that no data was requested for that page https://www.bbc.co.uk/news/video_and_audio/headlines/53631866/first-spacex-crewed-mission-lands-safely'  through the internal proxy.


This could indicate a couple of things:


1.  The page and video data is cached in your browser and not being requested again.  Hold the shift key down and click the firefox refresh button to do a hard load of the page, with AUTO on.

2.  The Firefox profile you are using is not configured to use the system proxy settings.  See  https://www.jaksta.com/support/windows/kb/firefox-not-detecting-https-streams-in-auto-mode-like-youtube-6000074222


From @

Thanks.

I set the Firefox proxy to "system proxy" and it now picks up the stream.

I have installed the v20 Beta and tried to record the same BBC link as above. It works!

I also set the preferred stream to 1080p and it ignored that to download the next highest at 720p.

So, success there too.

Thanks again.

The one thing that is disappointing, is that when downloading the BBC stream it comes up titled "Nothing to see here" and does not change once the recording has ended. I would assume it is not looking for a title in the places it should.


From @

AUTO mode naming is an "art form" not science as the stream protocol detected sometimes has no title in it and it is difficult to try and trace back to see what title is from - the fall back is the active window title at the time the stream is detected.

You have full control over the checks I try and do to detect a title

Settings > Internet Downloads > Advanced > Naming Rules.

image


The Properties > Progress log tab shows which naming rule was applied in there.


From @

Thanks.

I have all those set to on here. Maybe it is just the BBC who don't name their pages.


From @

Oooops!

Jaksta v21 has just reverted to the original "Unexpected error configuring the HTTPS/SSL monitor for Default LAN" message.

Does this mean I have to uninstall and reinstall again?

I have not been installing anything other than an Adobe Lightbox update.


From @

 logs attached


From @

Same issue as you originally had where a proxy cant be set on your machine.  

1.  WinHTTP Web Proxy Auto-Discovery Service is not running or enabled.

2.  A windows update has "broken" the proxy cfg in windows.


From @

Thanks.

It looks like I will have to edit the registry every time Windows updates. Seems a bit daft that it breaks things all the time. Can you not get Jaksta to check and turn it on every time it starts?


From @

JMR doesn't break it or edit that services or any other services registry entries.

In all these years you are the first person I have heard of that has this service switched off.  JMR (if running normally) won't have permission to start any services (as it doesn't need to do that).

Will definitely put a check in to prompt if that error is received with a bit more info to say that service might be down.


From @

Hey guys.


I don't want to hijack the thread but add my observations.

I rarely use "Auto". Normally I add a stream by pasteing it to Jaksta's own url bar. Because of this I didn't notice I get the same error as GregC when using auto.

1. I start Windows (complete reboot).
2. I start Jaksta.
3. I click on Auto.
That's the moment I get the error. And when I then click Auto again there's no error but Jaksta also doesn't discover streams.

However, when I now close Jaksta and re-open it and then click Auto again there is no error and the stream detection works perfect.

So basicly the only time the error occurs is the first time after a reboot and the first time clicking on Auto in Jaksta. This is only a small annoyance and I would not even have reported it till I saw this thread.

1. I use Chrome instead of Firefox.
2. My WinHTTP Web Proxy Auto-Discovery Service is set to manual and is running.
3. I can edit the proxy config in Windows/IE.
4. I have already re-installed Jaksta (to test something else). So that's not the problem either.

Long story short, I do NOT think this is a problem Jaksta causes. I do think that one of the Windows Updates during the last weeks caused this. Just like recently Windows Defender prevents changes to the HOSTS file I bet some Windows Update now interferes with Proxy changes.

Unfortunately I can't narrow it down since I rarely use "Auto", as I already wrote.

Good luck to you guys.


From @

This doesn't happen on the several test machines I have access to so not sure if its a windows update thing.

@andreas - can you provide debugs logs.  Reboot and turn debug logs on,  turn AUTO on - get the error - collect logs and post here, so I can see what is happening on your machine.


From @

I was finally getting to stay with relatives at the weekend and I checked their Windows 10 setup.

They too had the  WinHTTP Web Proxy Auto-Discovery Service disabled.

They don't use Jaksta so had not noticed it. It seems some Windows update has turned it off for some reason. They had Windows Home and I have Pro.


From @

I will keep an eye on it and report.


From @

Next release will check if this service is disabled and report.


From @

Thanks, that's a big help.


From @