aperture: Cannot run Aperture: unable to parse config file: invalid authenticator configuration
Hello, I am trying to get Aperture running on a server and I am receiving the following error when I run the aperture command after building:
unable to parse config file: invalid authenticator configuration
You can view the config I am using here and the diff from the defaults: https://github.com/lightninglabs/aperture/compare/master...secondl1ght:aperture:master
I have the auth disabled so I am not sure why it is not liking this config. All the changes made to the config were from following the instructions about setting up Aperture + a LNC Mailbox in the Builder’s Guide (https://docs.lightning.engineering/lightning-network-tools/aperture).
Any help to get this working would be appreciated. Thanks!
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Comments: 26 (11 by maintainers)
Ah ok cool, just to confirm this would still be secure in this particular use-case? Because the main traffic from the client is encrypted using HTTPS to the mailbox server but then internally the server uses HTTP to access the Aperture instance. So it is not actually insecure?
Sounds like Render does have a proxy that downgrades the connection to HTTP before it reaches the server. So I will have to use a different server hosting provider in order to get this working. I will make another attempt and I think it should work this time hopefully!
That probably either means your port 443 is already occupied. Or you need to run as root to listen on ports < 1024.
The parsing of this file works for me. Could you specify that config file when starting aperture, like
aperture --configfile=.... Maybe aperture isn’t picking up the right file?Since you have
disable: truefor the authenticator, you should never get that error message. So my suspicion is that the config file as a whole isn’t parsed correctly. Could very well be that our sample config has something weird in it that causes values to be ignored. Can you try starting from an empty config file just adding what you need? Or run the config file through a YAML parser and see if all values actually get picked up? Because YAML is susceptible to incorrect white space characters, maybe something isn’t properly indented or something like that.I am running locally.
I tagged you in a conversation on Slack where a user achieved the same setup that you are trying to set up. You might be able to get some info from them: https://lightningcommunity.slack.com/archives/C0112B0JYP2/p1696708659029809?thread_ts=1695837617.272239&cid=C0112B0JYP2.