Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to navigate from 'Topology' #24

Closed
lcondliffe opened this issue Jun 7, 2020 · 11 comments
Closed

Unable to navigate from 'Topology' #24

lcondliffe opened this issue Jun 7, 2020 · 11 comments
Assignees

Comments

@lcondliffe
Copy link

Hi,

I've setup the management console on an AWS instance using the repository instructions. I've registered an account and accessed the console but I can't navigate to any other pages (registries, vulnerabilities, settings etc.). It seems to be in a loop of 'resuming the live state' and is stuck 'Optimizing hosts'.

I've given it over 60 minutes as the readme mentioned, but there's been no change.

I can't find any obvious problems looking through the various container logs. I wondered if someone here could offer any guidance?

@sandman137
Copy link
Contributor

Hi @lwilliams1990 , can you confirm that the ec2 instance being used has 8 cores/16G RAM/120GB disk config as mentioned in the readme? Would also help if you can share a screengrab of the console while I try to reproduce the issue locally.

@sandman137
Copy link
Contributor

Quickly tried the installation at my end. Here is how it should look upon successful install.

You should see 1 host node on topology, Vulnerability db as a status on status bar. Menus Topology, Registries, Integrations and Settings should work as shown below. Other menus like compliance etc are disabled and will be removed from threatmapper screen as they don't belong here in community edition.

Topology screen

Screenshot 2020-06-07 at 8 58 14 PM

Registries
Screenshot 2020-06-07 at 9 01 10 PM

@lcondliffe
Copy link
Author

Hi,

Thanks for responding!

I gave it a c5.2xlarge aws instance with a 120gb root volume. I'm building the environment with Terraform / Ansible so I've just shared that publicly here:

https://github.com/lwilliams1990/deepfence-threatmapper-lab

The view I see when I connect in to the web console on the instance's public IP is this:

Screenshot from 2020-06-07 18-07-51

@shyam-dev
Copy link
Contributor

Hello @lwilliams1990 -

Can you please attach the output of the following command here --

for i in $(docker ps --format "table {{.Names}}");do echo "*****"$i"****">>/tmp/logs.txt;docker logs $i >> /tmp/logs.txt 2>&1 ;done

The output will be in the file /tmp/logs.txt.

On the face of it, this seems to be a configuration issue, and we will help you resolve it.

@shyam-dev
Copy link
Contributor

Also, are you using a VPN service ?

@lcondliffe
Copy link
Author

Thanks for your help! The requested logs are here:

logs.txt

I am using NordVPN on my laptop, I'm not sure why that would matter but I just tried provisioning and connecting in with it disabled and it is the same.

@shyam-dev
Copy link
Contributor

Hello @lwilliams1990

Thank you for sending out the logs to us.

Looking at the logs, this seems to be a client side issue. We use websockets extensively, and it is known that certain browser extensions and VPN software block connections to websockets.

Can you please try the following --

  1. Start a browser window in incognito mode, with all extensions disabled, and try to access the Management Console ?
  2. Try to access the management console from a different system ?

Thanks

@lcondliffe
Copy link
Author

Hi,

I've re-provisioned again using the same Terraform configuration previously mentioned to try again. I've tried with incognito and extensions disabled:

On Ubuntu 20.04:
Firefox 76.0.1 (64-bit)

Windows 10 1903:
Chrome 83.0.4103.61
Edge 83.0.478.44

I see the issue across all of these.

@sandman137
Copy link
Contributor

Thanks for sharing these details. Looks like we need to take a closer look, happy to help you triage live. Looks mostly like a config issue, not sure where though! Could you share your email at community at deepfence dot io. Will share hangout/slack details with you.

@ramanan-ravi
Copy link
Collaborator

Hello @lwilliams1990

Please join us on Slack here for support.

@lcondliffe
Copy link
Author

Issue was caused by the AWS security group rule being set as HTTPS instead of TCP/SecureTCP. This prevents Deepfence websockets working correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants