Community
Showing results for 
Search instead for 
Do you mean 
Reply

Act! Companion connection issues - cannot connect to self hosted instance of act!

Copper Contributor
Posts: 32
Country: Hong_Kong

Act! Companion connection issues - cannot connect to self hosted instance of act!

I have a copy of Act Premium v21.0.295.0, Update 5 running successfully, but I am now trying to get the Act! Companion to access my self hosted installation.

I’ve got Act Web running and I can access it both internally and externally through the web browser at https://act.[mydomain].com/apfw/

 

I can access the web api, again both internally and externally at https://act.[mydomain].com/act.web.api/

 

 

screenshot-api.png

 

 

 

 

 

 

 

 

 

I can log in successfully, both through the web interface and via the api: https://act.[mydomain].com/act.web.api/swagger/index.html (See attached screenshot)

 

I have a valid SSL cert.

 

However, when I try to use the Act! Companion mobile app, it will not let me connect.  I get a “User Login failed” message.  I am sure I am using the same username and password that I used for the web version, and I am using an "administrator" level username which has the access rights to the web api.

 

I was able to connect successfully with the Act! Companion to the trial database in the US.

 

I’m drawing blanks at this point and I don’t know what else to try to get the application working.

 

From the iis log files, I can see the following entries:


# successful login via the web api via web browser

2019-01-03 09:00:15 10.10.1.66 GET /act.web.api/authorize - 443 - 10.10.1.201 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/71.0.3578.98+Safari/537.36 https://act.[mydomain].com/act.web.api/swagger/index.html 200 0 0 5791


# attempt to use act! companion to access the same instance with the same username and password
2019-01-03 09:05:00 10.10.1.66 GET /act.web.api/api/system - 443 - 10.10.1.201 Mozilla/5.0+(iPhone;+CPU+iPhone+OS+12_1+like+Mac+OS+X)+AppleWebKit/605.1.15+(KHTML,+like+Gecko)+Mobile/16B92/vhdouzcxhdrwpgqmzeqcxzztivyntvxz http://localhost:9595/login 200 0 0 179
2019-01-03 09:05:00 10.10.1.66 OPTIONS /act.web.api/authorize - 443 - 10.10.1.201 Mozilla/5.0+(iPhone;+CPU+iPhone+OS+12_1+like+Mac+OS+X)+AppleWebKit/605.1.15+(KHTML,+like+Gecko)+Mobile/16B92/vhdouzcxhdrwpgqmzeqcxzztivyntvxz http://localhost:9595/login 404 0 2 0

 

 

Does anyone have any suggestions on how I might be able to debug or solve this problem further?

 

Thanks for your help.

 

- Paul

 

Nickel Elite Contributor
Posts: 600
Country: USA

Re: Act! Companion connection issues - cannot connect to self hosted instance of act!

Setup & configuration notes (just in case)

 

Requires an active Act! Premium subscription and use of either Act! API or Act! Connect Link depending on deployment method. 

 

 

Screen Shot 2019-01-03 at 8.57.26 AM.png

Juan Carlos Otero Garcia
juancarlosotero@protonmail.com
Twitter @MiInformativo
Copper Elite Contributor
Posts: 242
Country: Germany

Re: Act! Companion connection issues - cannot connect to self hosted instance of act!

Hi, are you using a Iphone or a Android based phone/Tablet?

 

we found that there may be a issue with android

 

regards

 

Ingo Lange

ACC since 1995
Developer of Addons for ACT

CrmAddon Factory
+1 208 56192-34
Copper Contributor
Posts: 32
Country: Hong_Kong

Re: Act! Companion connection issues - cannot connect to self hosted instance of act!

Hi Juan, yes, i have an active subscription and followed the installation guides. I’ll go through it again just in case I missed something.
Copper Contributor
Posts: 32
Country: Hong_Kong

Re: Act! Companion connection issues - cannot connect to self hosted instance of act!

Hi ilange

I’m running the iOS version
New Member
Posts: 3
Country: United_Kingdom

Re: Act! Companion connection issues - cannot connect to self hosted instance of act!

Did you make any progress with this issue in the end? I have been having a similar issue with v20.1 update 8 specifically, Swiftpage advised reinstalling Act on the server as a possible cause was due to the update being applied manually rather than Act being completely reinstalled with the update included, we know the API is working fine and can access this both internally and externally.

Thanks