NamelessMC

Internet Explorer

Internet Explorer is not supported. Please upgrade to a more modern browser.

Lupich

Member

Feed

There are no wall posts here yet.

About

Registered:
about 1 year ago
Last Seen:
about 1 year ago
Profile Views:
229
Minecraft
Lupich

Latest Posts

about 1 year ago
Unknown API error: nameless:missing_api_key

I should also note my issue is on a completely fresh installation as well.

about 1 year ago
Api key don't work

Very helpful for everyone else.... How did you fix it?

about 1 year ago
Unknown API error: nameless:missing_api_key

Hi All,

New to this software, pleasantly surprised to see 2.0 officially launched basically today. Great work I'm loving what I'm seeing so far! Dealing with some minor and expected glitches with something so new!

I configured /plugins/NamelessMC/main.yaml

From the Configuration > API section of my admin panel. API is enabled within that same page.

I am getting this error when I try to start my server, running spigot-1.19.2:

[23:08:48] [Craft Scheduler Thread - 0/ERROR]: [NamelessMC] Unexpected error: Unknown API error: nameless:missing_api_key
[23:08:48] [Craft Scheduler Thread - 0/ERROR]: [NamelessMC] com.namelessmc.plugin.lib.nameless-api.exception.NamelessException: Unknown API error: nameless:missing_api_key
        at com.namelessmc.plugin.lib.nameless-api.RequestHandler.makeConnection(RequestHandler.java:217)
        at com.namelessmc.plugin.lib.nameless-api.RequestHandler.get(RequestHandler.java:87)
        at com.namelessmc.plugin.lib.nameless-api.NamelessAPI.website(NamelessAPI.java:100)
        at com.namelessmc.plugin.common.ApiProvider.api(ApiProvider.java:120)
        at com.namelessmc.plugin.common.AbstractDataSender.lambda$run$3(AbstractDataSender.java:151)
        at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftTask.run(CraftTask.java:82)
        at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:833)

 

I've double checked anything I could think of, Googled it a bit but maybe it's too new of an issue?

Any assistance or suggestions would be appreciated!