Error with 1.8.1 webclient on login click - "There is a problem contacting the server!"

[Will Ford [Wake Forest]]

When I look at the logs in apache, I see the following errors- the first is always a 553 and then the rest of the attempts have the other number:

192.168.49.2 - - [09/Jul/2024:12:21:30 +0000] "POST /proxy.php HTTP/1.1" 200 553 "https://wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0"

192.168.49.2 - - [09/Jul/2024:12:23:14 +0000] "POST /proxy.php HTTP/1.1" 200 489 "https://wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0"

wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/i2b2/services/PMService?wsdl Looks good when I navigate to it

wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/i2b2_config_domains.json is configured with the following:

{
    "urlProxy": "/proxy.php",
    "urlFramework": "js-i2b2/",
    "lstDomains": [
        {
            "domain": "i2b2demo",
            "name": "staging",
            "urlCellPM": "https://WAZN-I2B2A-LX-1.medctr.ad.wfubmc.edu/i2b2/services/PMService/",
            "allowAnalysis": true,
            "debug": false
        }
    ]
}

changing debug to true hasn't provided me with additional information.

When I bring up the site, I do see a warning:

communicatorFactory: 'PM' does not have a cellURL specified - i2b2_cell_communicator.js:15

Then:

EVENT FIRED i2b2.events.afterCellInit[PM] - hive_globals.js:157

But when that alert modal comes up with the "There is a problem contacting the server!", nothing is written to the console to chase down. I did find the message in js-i2b2/hive/i2b2_cell_communicator.js:225

                      /* success handler code */
                      if (typeof o !== "object") {
                          alert("There is a problem contacting the server!");
                          return false;
                      }

But I'm not sure how to run this down.  Any help would be appreciated.

Thanks!

Will

[Wattanasin, Nich]

Hi Will,

I'm not sure if this will fix the problem, but try this inside i2b2_config_domains.json:

"urlProxy": "proxy.php",      (without the slash)

Thanks,

Nich

---

From: i2b2-ins...@googlegroups.com <i2b2-ins...@googlegroups.com> on behalf of Will Ford [Wake Forest] <wfor...@gmail.com>
Sent: Tuesday, July 9, 2024 8:44 AM
To: i2b2 Install Help <i2b2-ins...@googlegroups.com>
Subject: Error with 1.8.1 webclient on login click - "There is a problem contacting the server!"

 

        External Email - Use Caution        

--
You received this message because you are subscribed to the Google Groups "i2b2 Install Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to i2b2-install-h...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/i2b2-install-help/fbcea34a-97fe-4646-bc00-4438caf95758n%40googlegroups.com.

The information in this e-mail is intended only for the person to whom it is addressed.  If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Mass General Brigham Compliance HelpLine at https://www.massgeneralbrigham.org/complianceline .

Please note that this e-mail is not secure (encrypted).  If you do not wish to continue communication over unencrypted e-mail, please notify the sender of this message immediately.  Continuing to send or respond to e-mail after receiving this message means you understand and accept this risk and wish to continue to communicate over unencrypted e-mail. 

[Will Ford [Wake Forest]]

updated  wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/i2b2_config_domains.json and no change in outcome

{
    "urlProxy": "proxy.php",

    "urlFramework": "js-i2b2/",
    "lstDomains": [
        {
            "domain": "i2b2demo",
            "name": "staging",
            "urlCellPM": "https://WAZN-I2B2A-LX-1.medctr.ad.wfubmc.edu/i2b2/services/PMService/",
            "allowAnalysis": true,
            "debug": false
        }
    ]
}

[Wattanasin, Nich]

Thanks for the confirmation.

For the logs, do you see anything in your Apache error logs (might be in error.log or ssl_error log)?

Just to mention, the log entries that you pasted look fine (those look like from the Apache access log). The numbers '553' and '489' are not HTTP error codes, but the context length of the payload. The HTTP code that's actually being received is 200 which is good:

192.168.49.2 - - [09/Jul/2024:12:21:30 +0000] "POST /proxy.php HTTP/1.1" 200 553 "https://wazn-i2b2a-lx-1.medctr.ad.wfubmc.edu/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0"

Thanks,

Nich

---

From: i2b2-ins...@googlegroups.com <i2b2-ins...@googlegroups.com> on behalf of Will Ford [Wake Forest] <wfor...@gmail.com>

Sent: Tuesday, July 9, 2024 10:16 AM

To: i2b2 Install Help <i2b2-ins...@googlegroups.com>

Subject: Re: Error with 1.8.1 webclient on login click - "There is a problem contacting the server!"

 

To view this discussion on the web visit https://groups.google.com/d/msgid/i2b2-install-help/aab0104c-59e1-4bfa-9400-4f8fbfdb78bdn%40googlegroups.com.

[Will Ford [Wake Forest]]

This is within a Docker container.  I confirmed that the access.log and other_vhosts_access.log are symlinked to stout and  error.log to stderr, so these would show in docker logs but there's nothing additional coming through.

I can provide more details about what I've setup if that helps.

Thanks!

Will

[Vaibhav Talap]

Hi Will,

can you please provide more information about the setup you have using for i2b2.
Also let us know which docker image used for Webclient.



Thanks,

Persistent Systems Support Team

[Will Ford [Wake Forest]]

Sure!

I'm using php:8.2.20-apache-bullseye. Below is my Dockerfile.  I'm using a multistage build to reduce the layers in the final image.

```Dockerfile

FROM debian:stable as base

RUN apt-get update && \
    apt-get -y install \
    ca-certificates wget unzip

COPY certificates/* /usr/local/share/ca-certificates

RUN update-ca-certificates

RUN wget "https://github.com/i2b2/i2b2-webclient/archive/refs/tags/v1.8.1.0001.zip" -O /tmp/webclient.zip && \
    unzip /tmp/webclient.zip i2b2-webclient-*/* -d /tmp/ && \
    mv /tmp/i2b2-webclient-* /tmp/i2b2-webclient

FROM php:8.2.20-apache-bullseye

COPY --from=base /tmp/i2b2-webclient .

COPY --chmod=755 ./i2b2/webclient/etc/entrypoint.sh .

ENTRYPOINT ["./entrypoint.sh"]
```

The entrypoint script just dynamically generates the i2b2_config_domains.json and runs the apache2-foregound process.

```shell

#!/bin/sh
set -e

cat > "i2b2_config_domains.json" <<EOF

{
        "urlProxy": "proxy.php",
        "urlFramework": "js-i2b2/",
        "lstDomains": [

                {   "domain": "${I2B2_DOMAIN}",
                        "name": "${I2B2_DOMAIN_HUMAN}",
                        "urlCellPM": "${I2B2_PM_URL}",
                        "allowAnalysis": true,
                        "debug": false
                }
        ]
}
EOF

exec apache2-foreground

```

Thanks!

Will

[Vaibhav Talap]

Hello Will,

 

We have successfully created a Webclient docker image from your docker file and have been able to recreate the issue you reported.
Our team is currently investigating the root cause of the problem and will provide you with an update as soon as possible.

Thanks,

Persistent Systems Support Team

[Will Ford [Wake Forest]]

Thank you looking into this for us. Can you provide any status or expectations I can share with my management?

Thanks!

Will

[Vaibhav Palat]

Hello Will,

Apologies for the delayed response. We have built the web client image using our Dockerfile, but we are still facing the same issues.
Initially, we suspect the issue may be in the Proxy.php file. We are currently debugging it and will provide you with further updates soon.

Thanks,
Persistent Systems Support Team

[Vaibhav Talap]

Hello Will,

Apologies for the delayed response. We have built the webclient image using our Dockerfile, but we are still facing the same issues.
Initially, we suspect the issue may be in the Proxy.php file. We are currently debugging it and will provide you with further updates soon.

Thanks,
Persistent Systems Support Team