Unable to get RUM agent working - mixed content error

Elastic Community and Ecosystem Elastic Training
1

Course: Elastic Observability Engineer (On-Demand)
Version: 8.8.2
Question:

I have followed the labs in 3.4 and I see petclinic-react in Kibana Observability > APM > Services but it is not connecting to petclinic-node or sending the data needed in the further labs. I debugged my setup using the guidance in Unable to get RUM Agent working and noticed that my browser is probably the issue. I have tried with the latest Chrome and Firefox, where I disabled HTTPS-Only Mode. Now Developer Tools Console shows in the petclinic web page when refreshing the page:

Creating APM Service
Created APM Service
Blocked loading mixed active content “http://<my dynamic DNS>.labs.strigo.io:8200/intake/v2/rum/events”

petclinic-react Services Overview gives me “page-load” option but nothing else. I see also latency, throughtput and some transactions data. I have tried to get this working several days.

How can I get the rest of the data through? I have disabled VPN and checked my system compatibility and all seems to be ok.
Below are the views from APM Services

image
image854×340 36.4 KB

2

Hello @mirde and welcome :slight_smile:
Based on the information you provided:

Blocked loading mixed active content “http://.labs.strigo.io:8200/intake/v2/rum/events”
I believe the RUM Agent requires to have your Strigo Dynamic DNS name.
it is around step 3-4 in the Lab 3.4 instructions:

Screenshot 2025-11-28 at 10.18.32
Screenshot 2025-11-28 at 10.18.322726×782 151 KB

You should copy the address in order to update the `config.js`
file in the following steps as follow:

apm_server_js: process.env.ELASTIC_APM_SERVER_JS_URL || 'http://ecerjxsmiqdj5a3mb-635a90828abe31e35c984dba.labs.strigo.io:8200',

After that follow the instructions to restart the docker container.
Then from your chrome browser, connect to petclinic using your Dynamic DNS address:
http://<DYNAMIC_DNS>:4000
=> it should be something similar to:
http://ecerjxsmiqdj5a3mb-635a90828abe31e35c984dba.labs.strigo.io:4000”

Then refresh the Service Maps and you should have the link between: petclinic-react —> petclinic-node.
(The above would be describe as well at the beginning of the Labs 4.3)

I hope it will help.
Kind regards

3

Sorry, I failed to mention explicitly that the error message does contain my actual dynamic DNS. I just edited it to <my dynamic DNS> for this post.

4

My bad @mirde .

I just checked this post regarding Blocked loading mixed active content

Have you tried, what they suggested as a temporary fix to see if the content is not blocked ?:

Note that the temporary 'fix' is to click on the 'shield' icon in the top-left corner of the address bar and select 'Disable Protection on This Page', although this is not recommended for obvious reasons.

5

Those settings are probably managed by company policy as I can’t disable the protection.

6

Managed to get it working on Chrome with following steps:

  1. Chrome > Settings > Privacy and Security > Security: disable Always use secure connection

  2. Open your Petclinic web page

  3. Manually modify address to make sure you have http:your-dynamic-DNS:4000.
    This might get changed to https even when the previous settings are done.

  4. Click the “Not secure” icon on address bar and open Site settings

    image
    image392×338 19.8 KB

  5. Change “Insecure content” to Allow.

  6. Update your windows, clickedy click on Petclinic page and you should see petclinic-react in Services Map correctly and Events in petclinic-react Overview dropdown.

As a general note, I would hope that Elastic would take this kind of errors into considerations when creating these labs. Expecially when many people do the labs on company laptops where security settings are not so easy to change.

7

Many thanks @mirde for sharing here all the steps to solve the Blocked loading mixed active content issue you encounter. :+1: