WebTerminal not working with HealthConnect 2025.1
Hi,
I have just installed WebTerminal on my local instance of Health Connect 2025.1, but it does not work and returns a HTTP 401 error.
Can any one help, as I have never installed WebTerminal before?
Has there been any changes in Health Connect to stop it working in version 2025.1?
Thanks.
Neil
Comments
HTTP 401 means "Unauthorized" check that the web application /terminal has the correct credentials and correct authentication methods (password, LDAP etc.)
(the /terminalsocket should be always unauthenticated, its the default)
to help you resolve this, you may use auditing, to see if there is a "login failure" when you try to access.
It's definitely a login issue as I'm not always prompted to login or provide any credentials.
I have no idea why I don't always get a login prompt, but when I do WebTerminal does work.
Another challenge is to enable WebSocket protocol on your webserver
I just had the "pleasure" to do this for IIS 👺
It's not a default
Yes, I had enable WebSocket protocol on IIS, but when I use IIS, rather than InterSystems Private Web Server (PWS) I get a 404 error, rather than 401.
I'm trying this on two different instances, one using the PWS and one using IIS, with different errors, 401 or 404.