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

Question

Question

Why does Laserfiche 12 stop working when I block port 80, even though the entire installation and access was done solely through port 443 (HTTPS)?

asked one day ago

Hello everyone,

We successfully installed all components of Laserfiche 12 (including Directory Server, Web Access, Workflow, etc.) using port 443 exclusively, with a valid SSL certificate, and without ever enabling port 80.

Throughout the installation and initial testing, the environment worked perfectly with HTTPS-only access. However, when creating a firewall rule to explicitly block port 80, everything stopped working: the repository wouldn't load, Web Access failed, and services didn't seem to start properly.

The most confusing thing is that port 80 was never actively used, and there are no HTTP bindings configured in IIS, only HTTPS.

Does anyone know why Laserfiche keeps requiring port 80 to be free, even if it's not used directly?

Are there any internal services, verifications, or redirects that rely on port 80? How can it be configured to operate 100% under HTTPS and avoid this issue?

I greatly appreciate any help or similar experiences you can share.

0 0

Replies

replied 7 hours ago

A few of the components also use port 80 for administrative tasks, such as Import Agent, Server, Workflow triggers business processes using port 80. There is a really helpful whitepaper out there called "Default Network Ports for Laserfiche Products". The version I have is from February of this year, not sure if there is a newer version.

Hope that helps

Screenshot 2025-06-25 142217.jpg
Screenshot 2025-06-25 142246.jpg
Screenshot 2025-06-25 142315.jpg
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.