RADKit behind Squid Proxy

[dbillon]

Hi,

I'm trying to install RADKit 1.5.10 on Ubuntu 22.04 behind a Squid proxy.

I configured the proxy: (1) via the env var RADKIT_CLOUD_CLIENT_PROXY_URL and (2) via --setting cloud_client.proxy.url option from the radkit-service CLI. My proxy URL is something like: "http://proxy.my.lab:8080".

A few seconds after the launch RADKit Service seems to connect to the Cloud since I got the following message:
Connection to forwarder successful [uri='wss://prod.radkit-cloud.cisco.com/forwarder-1/websocket/']

Then I successfully login to the RADKit service portal but on this page the service status is displayed as "UNKNOWN" and I got an error message on the RADKit Service console.

You'll find RADKit service Python traceback in the file attached.

Any idea ?

BR,

Damien.

[Rana Khalil · Accepted solution]

Hello @dbillon ,

Thanks for reporting this.

Please share with me:

1- A screenshot of connectivity tab on RADKit service UI.

2- The status of RADKit service in CLI, is it showing as running?

3- Take a backup of ~/.radkit directory and share it with us.

Awaiting for your kind reply.

Best Regards,

Rana Khalil

[dbillon · Accepted solution]

Hi Rana,

Thanks for your help.

I use an Nginx proxy in front of the radkit-service (mapping https:443 => https:8081 on the same server).

The configuration of the "radkit-service" server in Nginx was not correct.

I share the configuration you gave me :

server {
  listen 443 ssl;
  server_name radkit-service.*;

  ssl_certificate /etc/nginx/ssl/nginx.crt;
  ssl_certificate_key /etc/nginx/ssl/nginx.key;

  location / {
    proxy_pass https://radkit-service:8081;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }
}

I works now !

BR,

Damien.

---

@Rana Khalil wrote:

Hello @dbillon ,

Thanks for reporting this.

Please share with me:

1- A screenshot of connectivity tab on RADKit service UI.

2- The status of RADKit service in CLI, is it showing as running?

3- Take a backup of ~/.radkit directory and share it with us.

Awaiting for your kind reply.

Best Regards,

Rana Khalil

---

[RobPrest]

Sorry to post this to an old thread, but I was having some real issues getting this to connect, and thought it worth posting my findings once resolved, to give some more context. Our setup was with Radkit running from docker, but with nginx proxying to 8081.

Although the radkit service connects outwards, the browser itself needs to be able to websocket into the local radkit service (so I was seeing lots of failed websocket connections in the Chrome debug console). It was the connection in to the local radkit rather than an issue with radkit communicating with the cloud that was stopping it from progressing.

Adding this part to the nginx config allowed the wss to go through, which then allowed us to enroll the SSO.

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';

This explains why setting it up locally worked, but it was failing when it was behind the nginx proxy. If you are seeing issues, it's worth checking for any javascript errors.

Kind regards

Rob