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

Question

Question

Can't start process in LF app

asked on June 1, 2017

Hi, I have a form that I want to use the app to start the process. But it won't work for me.

In a web browser, I can browse to http://CustomerName/forms and log in fine, start process and the form loads and submits file.

In the app, I can log into the repository fine, I can log into forms fine. Either, or and both work. But when I press on Start Process, it just waits and displays the loading circle.

I did some packet capture on my mobile device, the initial connection and browsing of the repository are using the customers internet IP http://110.142.2X2.XXX, but when I try and press start process the LF mobile app starts requests from the internal IP of http://192.168.10.252 and gets no data.

It doesn't make sense that a mobile App would request the internal IP range when its external most of the time. Have I misconfigured something, or mis understood something?

It works fine on Wifi locally and via VPN. 

Any ideas? 

 

Regards Gary

0 0

Replies

replied on June 6, 2017 Show version history

This is probably easier to troubleshoot in a support case but before that you should make sure that the Forms server is available externally (from a mobile web browser not thru VPN or local Wifi) and that the Forms server's external IP address is specified on the mobile server's configuration page. If for instance "localhost" is used and the two servers (Forms and mobile) are on the same machine, login would succeed (as that's between the 2 servers) but the mobile apps would fail to talk to the Forms server (to start the business process).

1 0
replied on June 7, 2017

Thank you for your reply.

The fix was as simple as confirming the correct port forwarding in the firewall and having the app server configuration pointing to the external IP.

 

However, the thing that was really throwing me through a loop, (not mentioned earlier) is the customer did not want port 80 for http traffic. So they had external port 85 forwarding to port 80 internally.

I don't think this can work with the mobile app as internally it would need http:80 and externally would need http:85.  The configuration works when on 80->80 OR 85->85

So the link in the app configuration would be incorrect for one of them at each given time if they want 85 ->80 

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

Sign in to reply to this post.