Invalid API key - after changing ports in 'config.xml'

Support
1

hi guys,

I’ve changed:

    <address>0.0.0.0:8384</address>

restarted systemd service and get:

$ stcli show connections 2020/06/13 11:04:27 getting config: Invalid API key

Is that normal & expected and if ‘yes’ then can you tell what happens there? many thanks, L

2

Not sure, I’d enable api loggging in syncthing and see why it refuses the credentials.

Usually cli gets the api key from the default config location, perhaps previously you did not run using systemd, and now that you do, it uses a different config location?

3

Or you now have another instance listning on 127.0.0.1:8384 where it couldn’t previously.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.