dsccommunity / dsccommunity/NetworkingDsc

The first byte of the proxy settings binary was '60' but should have been 0x46.

Open
#524 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs investigation
Dominant language
PowerShell
Stars
235
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Problem description

Received Error:
The first byte of the proxy settings binary was '60' but should have been 0x46.

But DefaultConnectionSettings and SavedLegacySettings is a completely fresh entry

image

Verbose logs
AUSFÜHRLICH: [xxx]:                            [[ProxySettings]ManualProxy] Test-TargetResource: Checking the CurrentUser proxy settings to ensure 'Present'.
AUSFÜHRLICH: [xxx]:                            [[ProxySettings]ManualProxy] Test-TargetResource: Checking that the CurrentUser proxy settings 'DefaultConnectionSettings' are in the desired state.
AUSFÜHRLICH: [xxx]: LCM:  [ BeendenTesten   ]  [[ProxySettings]ManualProxy]  in 0.1750 Sekunden.
Die PowerShell DSC-Ressource "DSC_ProxySettings" konnte die Funktion "Test-TargetResource" nicht ausführen. Fehlermeldung: "System.InvalidOperationException: The first byte of the proxy settings binary was '60' but should have been 0x46." 
    + CategoryInfo          : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : xxx
DSC configuration
ProxySettings ManualProxy
        {
            Target = 'CurrentUser'
            Ensure = 'Present'
            EnableAutoDetection = $false
            EnableAutoConfiguration = $false
            EnableManualProxy = $true
            ProxyServer = 'proxy.xxx.local:3128'
            ProxyServerExceptions = '*.xxx.local', '*.e-xxx.de', '*.xx.xxxx.de'
            ProxyServerBypassLocal = $true
        }
Suggested solution

Allow updating the proxy settings

Operating system the target node is running
OsName               : Microsoft Windows 10 Pro
OsOperatingSystemSKU : 48
OsArchitecture       : 64-Bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage           : de-DE
OsMuiLanguages       : {de-DE}
PowerShell version and build the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.19041.3031
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.3031
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
NetworkingDsc version
NetworkingDsc 9.0.0   C:\Program Files\WindowsPowerShell\Modules\NetworkingDsc\9.0.0\NetworkingDsc.psd1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ProxySettings ManualProxy resource and its Test-TargetResource entry point, focusing on the CurrentUser DefaultConnectionSettings and SavedLegacySettings values. Reproduce the failure on the reported Windows 10 and PowerShell 5.1 environment, then verify that the resource can update the proxy settings without the first-byte error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
infrastructure, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.