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

Discussion

Discussion

Use notification service on your mobile for LF App - Requires routing port 8181?

Mobile
Updated February 27, 2020
posted on October 7, 2019 • Show version history

I am just learning that the notifications feature on the mobile devices is hosted by the Laserfiche Notification Hub Service running the Laserfiche Server, which listens on port 8181.

Does this mean we need a route configured, so that port 8181 is accessible on our local Laserfiche server from an outside network like Verizon?

Here is the article support pointed me to when I told them it stopped working. The strange thing is, we never had routing for this port and it was working in older versions of the app.

https://laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/Forms/Content/Notification-Service.htm?TocPath=Forms|Configuring%2520Laserfiche%2520Forms|_____4

0 0
replied on October 7, 2019

The Laserfiche Notification Hub Service by default is installed on the same host as the Laserfiche Forms Server. The reason you are probably not getting notifications is that you have TLS1.0 disabled. I believe that's now disabled by default with a Windows Update (and only TLS1.2 is enabled).
We have a fix for that in the Notification Service which will be released with Forms 10..4.2.

If you need this working ASAP you can contact support to send you the patched binaries. Sorry for the inconvenience - when TLS1.0 got disabled a 3rd party component we use that pushes notifications to the Apple/Google clouds stopped working.

1 0
replied on October 10, 2019

Ah ok, thank you! I will update the support case with this information. So we do not need to route any ports from the outside? The documentation seems to discuss ports and I am not sure why that is if no routing needs to be done.

0 0
replied on February 27, 2020

Sure enough, right after installing Forms 10.4.2 all notifications started working without any additional configurations. So it was just an issue with the specific 10.4.1 build or maybe all previous builds since the TLS requirement.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...