Bad API key message

Support
1

Hi,
After passes steps to set up node and trying to “Set APi key” I have screen message - Bad APi key.
i’m typing my passwords, config file is as on template - see screens.
Please help
M.

ergo2
ergo22560×1440 82 KB

2

ergo1
ergo12560×1440 232 KB

3

I’m sure you’ve already tried it but just in case… did you try without quotes?

4

Please provide first lines of the log. But I am pretty sure that this is about config file can’t be read. As there are a lot of complaints like that I guess it would make sense to fail immediately during the launch if config parsing fails, made an issue about that Fail if config can't be parsed · Issue #1284 · ergoplatform/ergo · GitHub .

In your case, you can just remove lines with directories, I guess paths do not corresponding to Windows format. Then the node data sub-folder will be created in a folder you’re running the node launch command from.

5

I’m experiencing the same.

Host system is running centOS 8.3. Tried multiple keys, with or without quotes.

19:19:11.536 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(/opt/ergo/ergo.conf),Some(MainNet))
19:20:35.872 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(/opt/ergo/ergo.conf),Some(MainNet))
19:20:47.803 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(ergo.conf),Some(MainNet))
19:21:21.551 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(ergo.conf),Some(MainNet))
19:21:56.067 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(ergo.conf),Some(MainNet))
19:23:13.608 INFO  [main] org.ergoplatform.ErgoApp - Running with args: Args(Some(ergo.conf),Some(MainNet))

I’m not seeing anything out of the ordinary in the startup output.

Update #1:
I tried to directly access the system via curl using the example to get the API key hash:

curl -X POST <…>

but it would always tell me the port was closed. So, I tried forcing it to use ipv4 with an ‘–ipv4’ option with the curl and that worked.

I’m thinking that I have to deal with an IPv6 issue because if the calls are going through IPv6 they’re being blocked and that may explain the Bad API Key error. Maybe the calls through panel are defaulting to IPv6 and getting blocked would explain things.

Just not entirely sure how to properly remedy this. I made sure I made a rule for port 9053 for my home zone, yet still getting Bad API Key still.

Update 2:
I swapped out the name drive with another running a brand new Ubuntu 20.04.2 Server. Getting to the same point. Telling me Bad API Key.

I can’t pretty much eliminate the firewall issue because I used a web browser on another networked computer to access the panel (centOS had full GUI setup).

I’ve also tried multiple browsers. I use Safari a lot, so I fired up the development window and I do get a 403 response on any attempt to send the any API key via the popup dialog.

Update #3:
I rolled back to the 4.0.7 client, and it accepts the API hash … but only on Ubuntu.

Using centOS, either using 4.0.7 or 4.0.8 it still doesn’t accept the key.

6

So, after all of this, I think the issue might have been that I had “restAPI” when it could have been “restApi” instead.

1 Like