Repository navigation
Replies: 1 comment 2 replies
|
There are two separate things here, and the API-address behavior is reproducible. In v0.7.10's ./mycelium -c test.toml --api-addr 127.0.0.1:55551 routes selectedI checked this using the released v0.7.10 Windows executable against two temporary local HTTP listeners. With only the configured address, the GET went to port 8989. With For the key: ./mycelium -c test.toml -k /home/foo/.local/share/mycelium/node2.binThe binary name is also consistent with the release: |
Uh oh!
There was an error while loading. Please reload this page.
I am not even sure what's happening, but before I open an issue, let's ask around.
I'm trying mycelium first time. Downloaded binary artifacts, trying
mycelium(which is notmyceliumd, as documentation claims). It seems to work using command line. So I have picked the example config, started, works. Okay.So I wanted to test traffic between nodes, so I have create a second node config, like
The daemon starts (which is immediately a bad sign, since that key file does not exists at all; yeah, I see that it is not supposed to be used, but why?). Debug does not log plenty of the settings; what it does I can verify, so "4444*" numbers were changed, "5555*" were not logged by debug (or unchanged).
Okay, let's test:
./mycelium -c test.toml routes selected
As it turns out config selectively works, some stuff set things, others don't. Or else. I am confused how the config is supoed to work. Is this a bug or user error?
Though the user expects the config to configure what's in it, right?
All reactions