- Community Home
- >
- Software
- >
- HPE OneView
- >
- Who Me Too'd this topic
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2017 05:36 PM
11-22-2017 05:36 PM
HPE Oneview 3.10.07 cannot launch console, bad request 400
Hi there,
Recently i added two DL360 gen 10, Server 2016 servers, each licensed through Oneview with "HPE OneView Advanced".
Whenever i try to lauch a console from Oneview for either of these servers the black window pops up and fails when retrieving session settings via SSL "HTTP Error: The remote server returned an error: (400) Bad Request.
I have other gen 9 Window Server 2012R2 servers on the same IP subnet and i can view them remotely using the remote console.
These gen 10 servers are using the SPP 2017.10.01 bundle. The other servers are using an eariilier SPP build.
I did a packet trace and the SSL handshake completes successfully so i dont know how ssl is contributing to this issue.
Any thoughts?