You are viewing limited content. For full access, please sign in.

Question

Question

Unable to Verify Connectivity During Laserfiche 12 Upgrade (Offline Self-Hosted Environment)

asked on July 22

Dear Laserfiche Support Team,

I am currently using Laserfiche 12 Self-Hosted in an offline server environment and I am attempting to upgrade to the latest available version.

 

During the upgrade process, the installer requests access to the following endpoints:

Our network team has added these URLs to the firewall/proxy allow list.

To verify connectivity, we successfully tested TCP access on port 443 using the following commands

telnet d1oywsbnq10fc4.cloudfront.net 443
telnet infrapi.laserfiche.com 443
telnet laserfiche-support-site-downloads.s3.us-west-2.amazonaws.com 443

 

All three connections were successful, confirming that port 443 is reachable.

However, when we click "Verify Connection" in the Laserfiche Installer, the connectivity check still fails and displays the following error:


 

Please let us know if there are any additional URLs that need to be whitelisted or any other configuration changes or troubleshooting steps required to complete the upgrade successfully.

Thank you for your assistance, and we look forward to your guidance

0 0

Replies

replied on July 22

Hi Abdulrheem, this sounds like the same problem that is mentioned in this post: Installer endpoint connectivity - Laserfiche Answers

1 0
replied on July 22

Also check this post - there were two additional endpoints added on July 13, 2026

1 0
replied on July 22

Thank you, Mr.Craig Slack and Mr. Black Smith.

I have followed the update, but unfortunately the issue is still not resolved on my side.

I would like to add that when I test the update on my internet-connected machine, the connectivity verification completes successfully. However, when I test the update on the offline server—which has been granted access to the three required URLs mentioned earlier—the installer still reports the same connection verification error.

Could you please advise if there are any additional endpoints, prerequisites, or configuration steps that I should verify?

0 0
replied on August 5

Which version are you testing? The "Timedout 11010" message in the screenshot suggests you're running an older version. This was a bug in earlier releases related to endpoint verification and should be fixed in the latest version.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.