Unable to connect Diagnostics Console to remote server

[Dillon_Miller]

Background: We just upgraded to OnBase Foundation v19 EP2, and are looking to have our development team connect the Diagnostics Console installed on their workstations to a remote application server. Read through the Diagnostics Console MRG extensively, but am unable to get our team to connect.

So far, I have: 

1. Ensured that the 'Hyland Diagnostics Service' Windows service is running on the application server
   1. This service is ran by a domain account with permissions to everything OnBase-related on the server
2. Verified that I can access the Diagnostics Console locally from the application server
3. Used every variant of the application server's URL, with and without the 8989 port (not sure if that's necessary):
   1. https://hostname/AppServer/Service.asmx 
   2. http://hostname:8989
   3. http://hostname:8989/AppServer/Service.asmx
   4. etc, about fifteen different variations
4. Verified that from the developer workstation, they can successfully access the application server URL via web browser
5. Checked to make sure port 8989 was not blocked

I have never configured the Diagnostic Console for remote access. Not sure what else I can try here, and help would be greatly appreciated!

[Dillon_Miller]

Hi Jim,

Thanks for the comment. I have zero familiarity with JSON, and am using Foundation EP2 for reference. This may explain why I did not actually have the BindIP parameter in appsettings.json, just:

{

"Urls":http://localhost:8989"

} 

So I ended up replacing the contents of appsettings.json with the JSON file you posted, restarted the service, and was able to connect remotely using the following format:

http://hostname:8989

Thanks a ton for the help sir!

[James_Perry]

Happy to help. It was timely as I just figured it out today for our environment. 

I'm happy that Hyland continues to innovate and move towards the future but I find it difficult to keep up with the changes and minutia that needs to be hunted down, tested, and hope that what fixes the problem doesn't cause new ones. Being a one man shop, without the community I would not be able to upgrade or support our systems and modules.

A fine example of this is the 4 different ways this problem is resolved regarding version 17, 18, EP1, and EP2. The BindIP setting is probably deprecated for EP2. If you used this it may have worked.

{

"Urls":http://0.0.0.0:8989"

}