grbgetkey giving errors on AWS EC2 instances

Answered

Pengfei Zheng

August 31, 2021 05:35

• 
• 

We've set up ssh tunnels from EC2 instances to our univ computers. Then for licensing, we got the following error:

info : grbgetkey version 9.1.2, build v9.1.2rc0
info : Contacting Gurobi license server...
info : Communication failed, check your network connection or set variable HTTP_PROXY if you need a proxy
info : Run 'grbgetkey --help' for more details
error : dial tcp 127.0.0.1:443: connect: connection refused

0

• Official comment

  

  Simranjit Kaur

  • Gurobi Staff

  June 23, 2025 02:48 Edited

  This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum. Or why not try our AI Gurobot?.
• 

  Silke Horn

  • Gurobi Staff

  August 31, 2021 06:57

  We have assisted you in a support ticket, but I'll also post the gist of the answer here to help other users:

  We have dropped support for unencrypted HTTP connections to the license server for security reasons. Since encrypted HTTPS does not work together with SSH tunneling, you have to connect directly or via VPN to your university network to use grbgetkey.

  Have a look at this article for more information.

  0

Post is closed for comments.