Question
· Jun 9

Protocol Error between the Web Gateway and InterSystems IRIS

#Docker #FHIR #Web Gateway #InterSystems IRIS for Health

I have created a new docker stack with webgateway and IRIS for Health 2025.1. I have mapped the posts of wegateway like this:

  • 8743:443
  • 8780:80

I can access IRIS portal through 8743 without problems.

I also have created a FHIR repository, and I'm able to access it through 8743 port.

I have a web application, in another server with another domain, that connects to this FHIR repository. I have configured in FHIR endpoint the allowed origin to the domain of this application. But when I try to connect from this application to FHIR repository I have this error on Webgateway:

Protocol Error between the Web Gateway and InterSystems IRIS

This is a second instance that I'm configuring, with the first one I didn't see this error. Could this be because first instance runs in 8443 port? Or maybe it is because 2025.1 version? I don't know what to do...

Product version: IRIS 2025.1
$ZV: IRIS for UNIX (Ubuntu Server LTS for ARM64 Containers) 2025.1 (Build 225_1U) Fri May 16 2025 12:31:23 EDT [Health:8.2.2]
Discussion (3)2
Log in or sign up to continue
DC AI Bot · Jun 9

I can’t find the information you’re looking for. If you rephrase your question, I might be able to help. You can also explore the following resources:

  • "Extend Your Web Server Configuration with the Web Gateway" [1]
  • "Web Gateway Registry in InterSystems IRIS" [2]
  • "The Web Gateway: Serve InterSystems Web Applications and REST APIs to a Web Client" [3].

Sources:

0 0
Laura Blázquez ... · Jun 13

I found this article: https://community.intersystems.com/post/no-access-control-allow-origin-h...

This is what's happening to me from my web application (excluding the webgateway error, which I think simply the description isn't correct).

Checking the CSPSystem user, I've assigned it the role of the database where the FHIR repository is located, and it still doesn't work. However, if I assign it the %All role, it works. So, I'm missing some permission for this user; I can't figure out which one...

0 0