shabbzy

@leecalcote We dug around a bit to check the files and this is how we got it to work. docker run -d -p 443:443 --name=whd -e URL_HTTPS_PORT=443 -e HTTPS_PORT=443 solarwinds/whd-embedded:latest

@leecalcote Not really since we have our WHD containers behind a proxy which was acting as a SSL terminator we were not able to use SSO because the container was...

I forgot to mention change the Dockerfile to Expose 443 instead of 8081.

**This is the log for the agent:** > [root@ip-192-168-4-4 centos]# docker logs f32 starting agent network mode[host] container: f32ddf3afb81292fbdaf0a6f5491c93692c158dd675870521cebee361cfcc34d pid: 14537 inventory - NetworkMode is host skipping container f32ddf3afb81292fbdaf0a6f5491c93692c158dd675870521cebee361cfcc34d network...

I am using a service for the web ui, i did try removing the service, adding it again, adding the nodes/hosts again but still couldn't see the CPU and memory...

So, what could be causing this issue? I have 9090 open in the security groups and can also add nodes. Is it because I am running the web-ui as a...

@leecalcote Thank you for the response. I tried all the links as you mentioned and I can see the output. For example: > { "hostname": "ip-192-168-3-131.us-west-2.compute.internal", "architecture": "x86_64", "totalmemory": 7933190144,...