13:40:47 bongfrog: haproxy is correct. all is working except the monster-ui 13:43:08 able to log in to monster-ui with superadmin. but shows 'too many requests' error when attempting to retrieve accounts or numbers 13:43:47 api requests work i.e. http://x.x.x.x:8000/v2/accounts/....../children does show children accounts 13:45:29 kazoo log when trying to get accounts via monster-ui shows 13:45:30 PUT: /v2/user_auth? from x.x.x.x 13:45:30 PUT request fulfilled in 80 ms 435K816B mem 43K327B bin 13:45:30 over and over and over..... 13:46:45 i get this after a while in the log: bucket x.x.x.x/no_account does not have enough tokens(1 needed) for this request 14:23:27 maybe your superduper admin password is incorrect? 14:24:45 monster-ui accepts the password for login and API requests accept the credentials 14:25:41 errors occur only in monster-ui when trying to retrieve accounts and numbers. navigating through other features (users, devices, voicemails, etc.) works 15:15:45 mc_ Any news when v5 will be released? It is October already... 15:19:51 btracht: I would take a look and see if there are any clues in the dev tools on the browswer you are trying to access monster from. Might be ints in the responces of the user auth requests 15:23:01 bongfrog: thanks. dev tools shows the request going to the original domain 15:34:33 bongfrog: any idea how to correct this? 15:34:50 again, it only happens with accounts and numbers 17:09:42 btracht: That is a head scratcher, I would go through all of the doc in system_config and see if anything pops out there with the old Domain 17:35:43 if monster is sending req to original domain, check the monster config.js (or whatever its called) 17:35:49 and update the api_url 17:36:10 then clear browser cache and reload monster 17:36:23 mentax: am asking around to see if there's a more firm date 17:52:02 I think you will also need to run: sup crossbar_maintenance init_apps /var/www/html/monster-ui/apps http://${IP_ADDR}:8000/v2 17:58:11 mc_ BadRequest: i defined the api url in config.js and used sup command, did full reboot still same issue 17:58:24 ...only with numbers and accounts 18:00:14 btracht: Just to make sure, the {IP_ADDR} in there is asking for the IP address of the server where Kazoo (specifically) Crossbar API is running. 18:02:38 correct 18:02:45 this is on a AIO server 18:04:19 AIO? Do you mean the DB also lives within this server? 18:04:41 yes 18:04:53 So, you moved the whole AIO server somewhere else? 18:05:09 Under a different domain? 18:07:37 If so, I would suggest you to, first backup your /etc/kazoo/ folder and then follow this guide and perform the appropriate changes whenever you see "IP_ADDR" and/or "_HOSTNAME" being used within a command. 18:07:59 installed and configured kazoo applications, fs, couchdb on new server (new domain). just copied actual DBs 18:08:14 I see. 18:09:23 What error(s) do you see on the logs when you try to log in with an account besides master account. 18:09:30 ?* 18:09:49 Did you create this master account on the new installation or are you using the same you had before moving the DB to the new server? 18:10:58 using the original superadmin account. again, i only get the error when trying to access child accounts and numbers in monster-ui. i can get the child accounts and numbers of child accountsusing API requests 18:18:25 So, you can access any root account but not sub-accounts? 18:20:19 in monster-ui i can only get to account that i log into directly. clicking the dropdown tree or account app, just hangs and gives error 18:20:33 sounds like you need to compare your succeeding API req to the browser's attempt and see where they differ 18:22:36 the domain is wrong when attempting to get accounts. i have checked system_config caccount & rossbar docs. they all have the correct pvt_node. i'm thinking its a doc that i have not checked 18:22:44 but don't know which one 18:25:33 i have found a handful of docs in system_config with the original pvt_node that i have since changed. is there a way (sup command) i can sync the entire system_config DB with the updated domain? 18:26:45 not sure that that is even the issue, just something i noticed 18:48:23 bloody hell - activity.. i ask questions and there's no one for days lol 19:16:00 barney: lol 19:16:14 btracht: sup kapps_config flush 19:16:49 I think that commands takes care of flushing the old data out of the cache, so next time Kazoo tries to get that data, it will get the latest data from the config. 19:17:00 i think i tried that but i'll try it again 19:17:58 If it is outside system_config, you may need to use a more "aggressive" command but I guess it won't hurt on your cluster because it is not being used right now. 19:18:24 If that does not work for flushing the old information out of the cache, try running: sup kz_datamgr flush_cache_docs 19:34:30 no luck 19:34:57 still sending request to old domain 20:07:17 Oh, I think you need to reload Apache service after you modify config.js file for Monster-UI for the changes to take into effect. 20:07:24 sudo systemctl reload httpd.service 20:07:42 did that too 20:45:09 Not necessary to restart web server after config.js changes.