API error message every time page is loaded (For being british) #435

New issue

Open

opened 2026-05-22 13:42:58 -05:00 by GremlingThing · 2 comments

GremlingThing commented

2026-05-22 13:42:58 -05:00

(Migrated from github.com)

Describe the bug:

I just installed a fresh instance of voidauth and everytime I connect to the website; it generates an unhandled API error message which is:

ENOENT: no such file or directory, stat '/app/frontend/dist/browser/i18n/en-GB-oxendict.json

I think it's likely cause my browser's language setting is to use en-GB which doesn't exist as a localisation dictionary. I have no idea, thought I'd just log this error as it seems niche! Tried looking for a similar error listed but couldn't find any.

Only reason why I'm throwing this here is cause I wanted to set up fail2ban and this was triggering it off with my usual filters and yeah, others might have a similar problem who might not how to properly configure a filter on fail2ban (me included! I hate regex lmao)

To Reproduce:

Be british
Fill in the default docker compose and start running containers.
Use a cloudflare tunnel to the exposed port.
Connect to the website and observe logs.

Expected behavior:

No error message everytime I connect to my voidauth instance

Database Driver:

Default, posygres18 from docker compose.

Screenshots:

Additional context:

Running unraid.

### Describe the bug: I just installed a fresh instance of voidauth and everytime I connect to the website; it generates an unhandled API error message which is: > ENOENT: no such file or directory, stat '/app/frontend/dist/browser/i18n/en-GB-oxendict.json I think it's likely cause my browser's language setting is to use en-GB which doesn't exist as a localisation dictionary. I have no idea, thought I'd just log this error as it seems niche! Tried looking for a similar error listed but couldn't find any. Only reason why I'm throwing this here is cause I wanted to set up fail2ban and this was triggering it off with my usual filters and yeah, others might have a similar problem who might not how to properly configure a filter on fail2ban (me included! I hate regex lmao) ### To Reproduce: 1. Be british 2. Fill in the default docker compose and start running containers. 3. Use a cloudflare tunnel to the exposed port. 4. Connect to the website and observe logs. ### Expected behavior: No error message everytime I connect to my voidauth instance ### Database Driver: Default, posygres18 from docker compose. ### Screenshots: <img width="1169" height="541" alt="Image" src="https://github.com/user-attachments/assets/1a86b354-91e7-4789-a485-22a8b8eb0869" /> ### Additional context: Running unraid.

👍 1 😆 2

notquitenothing commented

2026-05-22 17:23:16 -05:00

(Migrated from github.com)

Thank you for opening an issue! I see where the problem is, I should be able to create a fix

notquitenothing commented

2026-06-04 23:31:25 -05:00

(Migrated from github.com)

This should be fixed in the latest release v1.13.0

This should be fixed in the latest release [v1.13.0](https://github.com/voidauth/voidauth/releases/tag/v1.13.0)