Question

weblink user unable to access repository

Version 10 Laserfiche WebLink

Updated May 2, 2024

asked on April 30, 2024

Just got back from LF Empower 2024 and weblink stops working for some strange reason. I ask my co workers if they made any changes to the network and they say no. regardless I ask them to ensure that the necessary ports to allow communication from external web server to internal app server are open. When I try to establish a connection in weblink designer I get this error message

when I try to setup "Public User" it seems like it takes the username and password we establish in Laserfiche admin console. Unfortunately after putting in the password nothing shows up, I would expect to see the repository we've allowed in the access rights of LF admin console. Instead we see nothing

We have checked SSL and those are good for another 3 months.

0 0

Replies

replied on April 30, 2024

From the error message in your initial screenshot, it could be a DNS issue where the external servers do not know how to contact the internal ones. You can try editing the hosts file on the external servers and add the server name and IP address of the internal servers that need to be communicated with.

0 0

replied on May 2, 2024

Thank you Blake, we checked that and hosts file is the same as it was when environment was put in place but I think the issue is related to a recent firewall upgrade. That was the only change in network. We made some changes to the firewall adding to the communication between the 2 servers and it fixed the issue, allowing external web server to see LF repository properly on Weblink. Oddly enough external server in DMZ cannot ping internal LF Server but weblink is still working.

still looking into this

0 0

replied on May 2, 2024

It is common for ping requests to be disabled in these scenarios. When enabled it makes for an easy way for those wanting to know what your servers are to find out, essentially giving them what they need to try and access your systems.

1 0

replied on May 2, 2024

Correct. Ping uses the ICMP protocol, which the firewall is almost definitely configured to block. Since the exception you've added is for TCP 80 or 443, you want to test with a tool that uses that protocol. So you can try something like `curl https://lfservername.example.com/lf/`. This will check both that the name resolves and that the remote machine is reachable.

0 0

You are not allowed to follow up in this post.

Question

Question

weblink user unable to access repository

Replies

Sign in to reply to this post.