BitShares Forum
Main => Technical Support => Topic started by: monsterer on October 09, 2014, 08:04:14 pm
-
Calling http_start_server in the console will stop the GUI client from displaying any market data; it essentially freezes, although you can still page between tabs.
-
Calling http_start_server in the console will stop the GUI client from displaying any market data; it essentially freezes, although you can still page between tabs.
from my understanding the http_server is already running.. so maybe you reset some configurations when you run that command
-
from my understanding the http_server is already running.. so maybe you reset some configurations when you run that command
I can't connect to it without issuing that console command - so I presumed it wasn't already running?
-
from my understanding the http_server is already running.. so maybe you reset some configurations when you run that command
I can't connect to it without issuing that console command - so I presumed it wasn't already running?
the GUI itself is a web wallet displayed in a built-in browser ... however there are TWO different RPC interfaces ... you should take a look at the config.json file in %APPDATA%\BitShares X .. there you can "enable" the RPC interface by default .. but you have to SET a port for it .. I recommend setting a port for the "http_rpc...." variable
-
the GUI itself is a web wallet displayed in a built-in browser ... however there are TWO different RPC interfaces ... you should take a look at the config.json file in %APPDATA%\BitShares X .. there you can "enable" the RPC interface by default .. but you have to SET a port for it .. I recommend setting a port for the "http_rpc...." variable
TBH I wasted a lot of time trying to get my app to connect to the authenticated RPC port - so I'm just using the HTTP port. The problem is, you can't connect to the HTTP port without running that command, which causes the client to lock up. :/