Error message with no error message inside

[gjorans]

Error message with no error message inside

[gjorans]

No console window saying anything.

However! I tried deleting the config.json file, restarting it and making a new API-key and with a fresh config file it now works. I have absolutely no idea what happened. Could I have written the wrong api key (even though I checked many times and even tried to create a new one and enter a new one yesterday)? That may very well be what happened.

I tried putting some random stuff in the api key now and it does give me that same blank error message. So it must be something that went wrong on the human end of it. Sorry if I have waisted your time.

[github-actions]

Welcome! Thanks for submitting your first AmigaGPT issue! Your issue will be looked at ASAP. <3

[gjorans]

did some additional testing to better pinpoint the problem. Changed into using roadshow and get the same problem. So my guess is that it is not related to uae as I was now using A2065. I also made a new API key to check if that was the problem. Same windows saying error with no message inside

[sacredbanana]

That is a strange one. I have tested it in UAE (via AmiKit) and it works well. I'll have a look around and try to figure out what's going on though. Thanks for the report.

[sacredbanana]

If you look in the directory where you have AmigaGPT installed, do you see a file called config.json? It could be an error creating that file.

[gjorans]

The file is there. I am attaching a screenshot of the content, but it looks to be in good shape to me. I have tried different models to rule out that as well. My setup is a plain installation of AmigaOS 3.2 with only AmigaGPT + those extras from your install guide (AmiSSL ++).

[sacredbanana]

Sometimes AmigaGPT will open a new console window to display errors. If you open the app in workbench mode instead of a new screen you'll be able to see the console window if it opens one. Can you let me know if it opened a console window displaying an error?

[sacredbanana]

Awesome! No wasted time! Now you have let me know to properly test bad API keys to make sure it handles errors properly. I'll look into that for the next update!

[sacredbanana]

I was confused at first because if it was a bsdsocket issue then this would happen:

[sacredbanana]

No matter what I try, I can't seem to ever be able to produce an empty error message

[sacredbanana]

Been months and unable to reproduce. Closing for now.