Interact not accessible from other machines

[zdenek.kabatek]

Hi,

we installed Interact in client environment. Locally (on Interact machine) everything works fine. When we try to access Interact (https://authentication.local) from other machines within client infrastructure we are getting error that it can't be reached. We updated hosts file with IP address of the Interact server we can see that the requests are going through the firewall but we are not getting anything back. We have self-signed certificates but I doubt there is any correlation with that.

Any hint or tip what the reason can be?

Thanks.

Regards,

Zdenek

------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

[joefarr]

Hi Zdeněk

There could be a few things going on here relating to the installation or certificates. This is one for support@blueprism.com and I'm sure this issue can be resolved for you and the client.

Thanks 

------------------------------
Joe Farr
Product Consultant
Blue Prism Limited
------------------------------

[rizistt]

Hi,

There are two things possible,

1. Navigate to IIS and bind that website with the IP address assigned to that machine
2. Use a DNS in your client environment, patching the host file on each machine is a time-consuming thing - although that works too.

Let me know if that solves the issue.

------------------------------
Rizwan Tayyab
------------------------------

[zdenek.kabatek]

Hi, Rizwan,

we tried that and when we changed the IP address binding we can't even login into the Interact on the local machine where it is installed.

Regards,

Zdenek


------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

[RyanAndrews]

Hi Zdenek,

There are a number of websites which need to be resolvable for the functioning of interact, these include all the websites for hub. My recommended approach is to never use the default URLs, as these are only resolvable locally (they are added to the local hosts file on the hub/interact server during installation). Instead replace the .local with your internal domain name and then configure Host A records for all 11 records below in your internal domains DNS (E.G. Authentication.domain.internal) all host records should point to the same IP address of the Hub/interact server and none of the websites should be bound to an IP (leave as all unassigned)

Website in IIS	Default URL
Blue Prism – Authentication Server	https://authentication.local
Blue Prism – Hub	https://hub.local
Blue Prism – Email	https://email.local
Blue Prism – Audit Service	https://audit.local
Blue Prism – File Service	https://file.local
Blue Prism – Notification Center	https://notification.local
Blue Prism – License Manager	https://license.local
Blue Prism – SignalR	https://signalr.local

Blue Prism – Interact	https://interact.local
Blue Prism – IADA	https://iada.local
Blue Prism – Interact Remote API	https://interactremoteapi.local

------------------------------
Ryan Andrews
Platform Consultant
Blue Prism
Australia/Brisbane
------------------------------