-
Notifications
You must be signed in to change notification settings - Fork 39
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
Dig UI not being displayed #282
Comments
@saggu Do you have any sense of why the UI is not loading? Also, what is the status of this project? I see no new updates for about 18 months. Are there subsequent projects that have more active code contribution that we should be paying attention to? |
@jgerardsimcock there has been some issues after chrome update 80. We are currently working on a new version. There will be a new release soon. |
Thank you very much @saggu |
I can confirm I am having the same issue. I am running Dig inside a libvirt virtual machine using Vagrant. I set the DOMAIN in .env to the IP of the VM. Initially started docker with |
Any update regarding this? I am getting following errors:
I'm using Firefox as my default browser. |
@saggu ..... Getting the above errors at my end.
[2021-06-17T07:20:10,521][ERROR][logstash.agent ] failed to fetch pipeline configuration {:message=>"No config files found: /usr/share/logstash/pipeline. Can you make sure this path is a logstash config file?"}
[2021-06-17T07:19:58,681][INFO ][o.e.n.Node ] [wfXSPoP] starting ... [2021-06-17T07:19:59,145][INFO ][o.e.t.TransportService ] [wfXSPoP] publish_address {172.19.0.3:9300}, bound_addresses {0.0.0.0:9300} [2021-06-17T07:19:59,175][INFO ][o.e.b.BootstrapChecks ] [wfXSPoP] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks ERROR: [1] bootstrap checks failed [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] [2021-06-17T07:19:59,219][INFO ][o.e.n.Node ] [wfXSPoP] stopping ... [2021-06-17T07:19:59,371][INFO ][o.e.n.Node ] [wfXSPoP] stopped [2021-06-17T07:19:59,372][INFO ][o.e.n.Node ] [wfXSPoP] closing ... [2021-06-17T07:19:59,415][INFO ][o.e.n.Node ] [wfXSPoP] closed Help me to come out the issue. |
The reason the UI is not working is because mydig-webservice/frontend relies on HTML imports, a feature that was only ever implemented on Chrome browser and which even Chrome has since deprecated. The following workaround works for me.
FROM uscisii2/mydig_ws:2.0.4
COPY frontend /app/mydig-webservice/frontend
|
As a disclaimer this could be an issue with the fact I haven't used Docker before*
I followed the installation instructions, etc, everything seems to be installed fine with no errors, the web server starts up, when I navigate to it on Chrome, the Dig UI is completely blank, when I view the source there is certainly something being loaded, however it doesn't seem to be displayed.
The text was updated successfully, but these errors were encountered: