Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Google Chrome Returning 410 error #698

Closed
2 tasks done
Rorymon opened this issue Jun 5, 2024 · 3 comments
Closed
2 tasks done

[Bug]: Google Chrome Returning 410 error #698

Rorymon opened this issue Jun 5, 2024 · 3 comments

Comments

@Rorymon
Copy link

Rorymon commented Jun 5, 2024

What happened?

Google Chrome returns: The remote server returned an error: (410) Gone. This has been ongoing for several hours.

Version

2405.1076

What PowerShell edition/s are you running Evergreen on?

Windows PowerShell

Which operating system/s are you running Evergreen on?

Windows 10+

Have you reviewed the documentation?

Verbose output

VERBOSE: Function path: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2301.787\Apps\Get-GoogleChrome.ps1
VERBOSE: Function exists: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2301.787\Apps\Get-GoogleChrome.ps1.
VERBOSE: Dot sourcing: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2301.787\Apps\Get-GoogleChrome.ps1.
VERBOSE: Get-FunctionResource: read application resource strings from [C:\Program
Files\WindowsPowerShell\Modules\Evergreen\2301.787\Manifests\GoogleChrome.json]
VERBOSE: Calling: Get-GoogleChrome.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: UseBasicParsing: True.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: MaximumRedirection: 2.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: DisableKeepAlive: True.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: UserAgent: Mozilla/5.0 (Windows NT; Windows NT 10.0;
en-IE) AppleWebKit/534.6 (KHTML, like Gecko) Chrome/7.0.500.0 Safari/534.6.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: Method: Default.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: Uri: https://omahaproxy.appspot.com/json.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: ContentType: application/json; charset=utf-8.
VERBOSE: GET with 0-byte payload
WARNING: Invoke-RestMethodWrapper: Error at URI: https://omahaproxy.appspot.com/json.
WARNING: Invoke-RestMethodWrapper: Error encountered: The remote server returned an error: (410) Gone..
WARNING: Invoke-RestMethodWrapper: For troubleshooting steps see: https://stealthpuppy.com/evergreen/troubleshoot/.
Get-EvergreenApp : Internal application function: C:\Program
Files\WindowsPowerShell\Modules\Evergreen\2301.787\Apps\Get-GoogleChrome.ps1, failed with error: The remote server
returned an error: (410) Gone.
At line:1 char:1
+ Get-EvergreenApp GoogleChrome -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-EvergreenApp

VERBOSE: Performing the operation "Return output" on target "C:\Program
Files\WindowsPowerShell\Modules\Evergreen\2301.787\Apps\Get-GoogleChrome.ps1".
Application function Get-GoogleChrome ran, but we failed to capture any output.
Run 'Get-EvergreenApp -Name GoogleChrome -Verbose' to review additional details.
At C:\Program Files\WindowsPowerShell\Modules\Evergreen\2301.787\Public\Get-EvergreenApp.ps1:97 char:21
+                     throw [System.NullReferenceException]::New($Msg)
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], NullReferenceException
    + FullyQualifiedErrorId : Application function Get-GoogleChrome ran, but we failed to capture any output.
Run 'Get-EvergreenApp -Name GoogleChrome -Verbose' to review additional details.
@Rorymon Rorymon added the bug Something isn't working label Jun 5, 2024
@aaronparker aaronparker removed the bug Something isn't working label Jun 5, 2024
@aaronparker
Copy link
Owner

You need to update Evergreen. You're on 2301.787, the latest is 2405.1076

@Rorymon
Copy link
Author

Rorymon commented Jun 6, 2024

That was odd, I read the troubleshooting doc and ran the update before posting. (Update-Module -Name Evergreen -Force)

I tried again this morning without running the update first and it is working now without any changes. May have been an intermittent issue that lasted a while. I will re-run the update again. Thanks!

@aaronparker
Copy link
Owner

You may have needed to add Import-Module Evergreen -Force after an update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants