iOS Question My bridge app will not install from Safari

[davepamn]

My problem is the b4ibuilderserver wants me to use xx.xx.129.2:51041 port. I don't have an static ip address on my iMac. I used my imac address in b4i for the server ip. That worked. However, when I go to install bridge on the ipad, it tries to access xx.xx.129.2

Is there a way to change the b4ibuildserver ip address?

I was able to user the key.txt to override the ip address

manual:xx.xx.102.32

 

[davepamn]

Build server version: 1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2014-11-20 11:29:23.847:INFO::main: Logging initialized @123ms

Loading default configuration file.

AppPath=/Users/xxxxxx/Documents/Development/macserver-aa

2014-11-20 11:29:23.935:INFOejs.Server:main: jetty-9.1.z-SNAPSHOT

2014-11-20 11:29:23.954:WARNejh.MimeTypes:main: java.util.MissingResourceException: Can't find bundle for base name org/eclipse/jetty/http/encoding, locale en_US

2014-11-20 11:29:23.967:INFOejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@73035e27{/,file:/Users/xxxxx/Documents/Development/macserver-aa/www,AVAILABLE}

2014-11-20 11:29:23.968:INFOejs.AbstractNCSARequestLog:main: Opened /Users/xxxxxx/Documents/Development/macserver-aa/logs/b4j-2014_11_20.request.log

2014-11-20 11:29:23.986:INFOejs.ServerConnector:main: Started ServerConnector@3ab39c39{HTTP/1.1}{0.0.0.0:51041}

2014-11-20 11:29:24.154:INFOejs.ServerConnector:main: Started ServerConnector@d44fc21{SSL-http/1.1}{0.0.0.0:51042}

2014-11-20 11:29:24.155:INFOejs.Server:main: Started @436ms

Build server is ready

---There are warnings in the list. Does that matter?

Do I need to install Eclipse

 

[davepamn]

So the Mac key is wrong.

You need to stop the Mac builder, delete all the files under the key folder (on your Mac) and start the build server.

Should I remove the macserver-aa directory and start over?

 

[Erel]

---There are warnings in the list. Does that matter?

No.

Should I remove the macserver-aa directory and start over?

No. You should only do exactly as written in the instructions.

 

[davepamn]

https://xx.xx.102.32:51042 WORKED!

There must be a network policy that enforced that usage of a secure socket.

Yeah!