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.

Sign up for GitHub

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

Jump to bottom

REST timeout since Nessus upgrade to v7.0.1 #20

Open
tschuh-vazata opened this issue Jan 16, 2018 · 3 comments
Open

REST timeout since Nessus upgrade to v7.0.1 #20

tschuh-vazata opened this issue Jan 16, 2018 · 3 comments

Comments

@tschuh-vazata
Copy link

tschuh-vazata commented Jan 16, 2018 •
edited
Loading

New-NessusSession times out on instantiation since upgrading our Nessus instance to 7.0.1 (Windows 2012R2). I can log in to the Nessus server via browser with the same credentials.
@tschuh-vazata
Copy link
Author

tschuh-vazata commented Jan 16, 2018 •
edited
Loading 

VERBOSE: POST https://<ServerIP>:8834/session with -1-byte payload
Invoke-RestMethod : The operation has timed out
At C:\Users\tschuh\Documents\WindowsPowerShell\Modules\Posh-Nessus\Session.ps1:78 char:30
+             $TokenResponse = Invoke-RestMethod @RestMethodParams
+                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Packet analyzer shows:

<title>400 Bad Request</title></head><body><h1>Bad Request</h1><p>Your browser sent a request that this server could not understand.<br>Reason: You're speaking plain HTTP to an SSL-enabled server port.<br>Instead, please use the HTTPS scheme to access this URL.<br></p></body></html>

If the Write-Verbose output is to be trusted (no reason not to) then we're already submitting the POST via HTTPS.

@darkoperator
Copy link
Contributor

darkoperator commented Jan 16, 2018 via email

@tschuh-vazata
Copy link
Author

New-NessusSession

I resolved it moments ago by manually removing the module and reinstalling from Git. It seems Remove-Module did not perform as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@darkoperator @tschuh-vazata