-
Notifications
You must be signed in to change notification settings - Fork 377
Page not loading, "Oops... Something went wrong" #43
Comments
Thanks for looking into this, I must say that I'm the same guy who posted this issue. So just a reminder, I'm running this (Ubuntu 16.04 with 4Gb ram and 60Gb Drive) as an lxc container on proxmox. |
Hello, The problem is Run |
Thanks for that info, I found out that on Proxmox (running LXC containers) this setting needs to be done at the host level (when I did it within the ubuntu container it said read-only). I'm glad that is resolved but still having trouble starting ambar. Now when I check the docker logs ambar_es_1 it tells me...
On the front end chrome dev tools tells me it's still having trouble connecting to the /api/ |
@tscibilia I don't see any problems in logs, update to latest version and try again |
@tscibilia any news? |
No response for 2 weeks |
Sorry about not responding, I gave up on it. however, I just noticed there was a new web api commit today v1.2.0 So I did ./ambar.py uninstall and then reinstalled everything. Now it works! |
I appear to be having the same issue (or similar) as the OP (agreenfield1) did here. Any advise or assist based on the data below (PS I aready tried changing the http://es:9200 to the actual ip address but it didn't help?
./ambar.py start
http://192.168.5.122:80/_cat/indices
Just returns a blank page
website console errors
docker logs ambar_webapi_1
docker logs ambar_es_1
File: config.json
File: docker-compose.yml
The text was updated successfully, but these errors were encountered: