bug: On creating username UNKNOWNERROR #119

New Issue

2026-02-16T12:51:30-05:00

yindo commented

2026-02-16 12:51:30 -05:00

Originally created by @flemtastic on GitHub (Sep 17, 2025).

What happened?

After creating an account successfully, and first log in, we're prompted to create a username. Submitting the username results in an Unknown Error. Entering again results in an ALREADYONBOARDED error.

Potential environment issues:

I am running this behind NGINX, being pointed to Caddy.
- .env.web has HOSTNAME=:80

Originally created by @flemtastic on GitHub (Sep 17, 2025). ### What happened? After creating an account successfully, and first log in, we're prompted to create a username. Submitting the username results in an Unknown Error. Entering again results in an ALREADYONBOARDED error. Potential environment issues: - I am running this behind NGINX, being pointed to Caddy. - .env.web has HOSTNAME=:80 <img width="482" height="268" alt="Image" src="https://github.com/user-attachments/assets/a8ba6014-5ceb-4e21-9f3f-14ad38b719ab" /> <img width="481" height="251" alt="Image" src="https://github.com/user-attachments/assets/57b0fbcd-cef6-4699-9e05-7305526118de" />

yindo added the bug label 2026-02-16 12:51:30 -05:00

yindo commented

2026-02-16 12:51:30 -05:00

@flemtastic commented on GitHub (Sep 17, 2025):

For further clarity, I have the app, api, events, etc urls hardcoded to https://, but also was getting the same error with http://

@flemtastic commented on GitHub (Sep 17, 2025): For further clarity, I have the app, api, events, etc urls hardcoded to https://, but also was getting the same error with http:// <img width="798" height="187" alt="Image" src="https://github.com/user-attachments/assets/e4811a23-d1e0-4f34-926b-507724b0c50e" />

yindo commented

2026-02-16 12:51:30 -05:00

@dillacorn commented on GitHub (Sep 23, 2025):

Yepp same.. I'm moving on to something else now.. this sucks - not going to troubleshoot any further.. - someone let me know if it's resolved and I'll come back to try again!

@dillacorn commented on GitHub (Sep 23, 2025): Yepp same.. I'm moving on to something else now.. this sucks - not going to troubleshoot any further.. - someone let me know if it's resolved and I'll come back to try again!

yindo commented

2026-02-16 12:51:30 -05:00

@Daniel13850 commented on GitHub (Sep 30, 2025):

I have the same problem with exact that same setup.
I hope someone solves the issue.

@Daniel13850 commented on GitHub (Sep 30, 2025): I have the same problem with exact that same setup. I hope someone solves the issue.

yindo commented

2026-02-16 12:51:30 -05:00

@Daniel13850 commented on GitHub (Sep 30, 2025):

I have found the solution!

You need to add this lines to your nginx website config inside the location block:

# WebSocket support
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

Source: https://stackoverflow.com/a/39216976

@Daniel13850 commented on GitHub (Sep 30, 2025): I have found the solution! You need to add this lines to your nginx website config inside the location block: ``` # WebSocket support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; ``` Source: https://stackoverflow.com/a/39216976

yindo commented

2026-02-16 12:51:30 -05:00

@tristan-mastrodicasa commented on GitHub (Nov 9, 2025):

Downgrade all https urls to http, and wss to ws.
Make sure all URL's have the same domain / IP in the toml and env file
Delete the cached data in data

@tristan-mastrodicasa commented on GitHub (Nov 9, 2025): Downgrade all `https` urls to `http`, and `wss` to `ws`. Make sure all URL's have the same domain / IP in the toml and env file Delete the cached data in `data`

yindo commented

2026-02-16 12:51:30 -05:00

@Enverex commented on GitHub (Feb 9, 2026):

That may solve the original issue, but how do you now solve the "AlreadyOnboarded" error?
EDIT: I take that back, that doesn't fix the original issue either. Both problems still occur.

@Enverex commented on GitHub (Feb 9, 2026): That may solve the original issue, but how do you now solve the "AlreadyOnboarded" error? EDIT: I take that back, that doesn't fix the original issue either. Both problems still occur.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#119