GET https://my.jmp.com/ "Connection timed out after 10003 milliseconds for JMP18.2.2 and JMP19

[#1]

Hello other JMP users. I have been working a particular cybersecurity issue we are seeing with JMP18.2.2 and higher. Was due to some changes JMP made, and we have been working with JMP Support. It still appears to be on our side for firewall or proxy, so wanted to see if any other JMP users had the same problem and were able to resolve with their IT department. This is for Windows 11.

When we launch JMP18.2.2, there is a 10 second pause. In the log, we see:

GET https://my.jmp.com/
Connection timed out after 10003 milliseconds

What is strange is that we can easily go to "my.jmp.com" from a browser, that is not blocked, but some communication protocol or handshake is blocked.

We are still able to use JMP after that. It is just a small inconvenience to wait the 10 seconds each time it is launched.

We are able to replicate with the suggested New HTTP Request testing in JSL:

Names Default To Here( 1 );
baseURL = "https://my.jmp.com";
request = New HTTP Request( URL( baseURL ), Method( "GET" ), Timeout (5) );
request << Send;
Write( "\!n" || Char( request << Get Status Message ) || "\!n" );

We then get in the JSL script editor embedded log (note I changed Timeout to 5 seconds to speed up the testing)

GET https://my.jmp.com/
Connection timed out after 5007 milliseconds

If we put in our Proxy and our port values, we can get the script to work with no timeout:

GET https://my.jmp.com/
Via: "our proxy"...

But after saving the preferences, this does not change the 10 second time out when JMP18.2.2 is launched again.

It will be worse for JMP19, which we are about to roll out. Now there are 2 calls, for a total of 20 seconds of delay.

GET https://my.jmp.com/
Connection timed out after 10007 milliseconds
GET https://activate.jmp.com/_jmpsoftwarestore/cgi-bin/go.cgi/webstore/XMLActivation
Connection timed out after 10015 milliseconds

Has anyone else seen this issue, and in particular, is there fix on the user side?

FYI, if you get the JMPStartup file (which JMP Support told me how to save), it is these steps where "checkForInternet", you can see the 10 second delays.

2025-10-13T14:39:46.774Z - License check
2025-10-13T14:39:46.774Z - Auth: Check saved license
2025-10-13T14:39:46.784Z - Auth VL1: Valid
2025-10-13T14:39:46.784Z - checkForInternet: Initiating
2025-10-13T14:39:56.855Z - checkForInternet(MyJMP): Status =28
2025-10-13T14:40:06.900Z - checkForInternet(Authorization): Status =28
2025-10-13T14:40:06.900Z - Auth: Valid license
2025-10-13T14:40:06.905Z - Auth VL2: Valid
2025-10-13T14:40:06.905Z - Auth: Product: JMP Name: JMP Release: 19

[#2]

You'll want to check with your network admin.

They may have the address blocked without the proxy.

[#3]

Is there a way to block the address without the proxy? Maybe I am not understanding what to look for.

Yes, we worked with our network admin. They removed all proxy blocking, was able to get to several normally disallowed sites, but something is still blocking the handshake for JMP. I can open the websites on my web browsers, it is just that JMP is not seeing something when it launches. I can easily ping the websites using the JMP script above.  The admins say they are not blocking my.jmp.com, but maybe there is some other cybersecurity setting they are not looking at. 

I may not be communicating to our network admins correctly what is going on, so was wondering if anyone else had this experience and was able to solve it.

[#4]

Most networks don't need a proxy, but every network can be different.

One other thing to check for is security certificates. You are using an https address which means ssl is enforced and certificates are used and verified.

You can try:

request = New HTTP Request( URL( baseURL ), Method( "GET" ), Timeout (5), Insecure(1) );

 Which will turn off ssl certificate verification. That's really not a long term solution, but it will let you know if the site is blocked or if it just can establish https.

[#5]

Could you try speeding up the launch by disabling the network connection (e.g. logging off the Wi-Fi or disconnecting the LAN cable)?