That is what I would expect to see if the proxy were not configured correctly.
On Tue, Apr 11, 2017 at 4:18 PM, Laurens Vets <laur...@daemon.be> wrote: > These are the errors I see when don't use the http option: > > [HPM] Error occurred while trying to proxy request /api/v1/user from > node1:4200 to 192.168.66.121:8082 (EINVAL) (https://nodejs.org/api/errors > .html#errors_common_system_errors) > [HPM] Error occurred while trying to proxy request /api/v1/user from > node1:4200 to 192.168.66.121:8082 (EINVAL) (https://nodejs.org/api/errors > .html#errors_common_system_errors) > > > On 2017-04-11 14:08, Ryan Merriman wrote: > >> The -r option shouldn't be that sensitive. Separate host and port >> properties would be better. >> >> On Tue, Apr 11, 2017 at 4:04 PM, Laurens Vets <laur...@daemon.be> wrote: >> >> On 2017-04-11 12:44, zeo...@gmail.com wrote: >>> <snip> >>> >>> scp >>> >>>> ./metron-interface/metron-config/target/metron-config-0.3.1- >>>> archive.tar.gz >>>> root@node1:/usr/metron/0.3.1/ >>>> ssh root@node1 >>>> cd /usr/metron/0.3.1/ >>>> tar -xf metron-config-0.3.1-archive.tar.gz >>>> yum install -y npm >>>> npm install npm@3.8.9 -g >>>> export METRON_REST_URL=http://node1:8082 >>>> ./bin/start_management_ui.sh >>>> >>>> I had to make sure to specify "-p 4200 -r http://node1:8082"; to >>>> server.js >>>> >>>> >>> FYI, if you use "-r node1:8082" instead of "-r http://node1:8082";, you >>> can't login. I had to find that out the hard way. >>> >>> <snip> >>> >>>
