-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Changes to API endpoints .env not being respected #96
Comments
Hi, |
Thank you for the quick response. So, yes, it solved the original issue. I'd recommend modifying the
as, for some odd reason, it was attempting to create a This new problem is most likely out of scope of this issue. I'm dealing with:
I tried changing the all the entries in the If you have any suggestions, they'd be much appreciated. Otherwise, feel free to close this issue. |
Thanks for notifying me about the Revolt.toml issue. Hadn't encountered that in my testing and I'll be sure to update it. As for the http error, I'd suggest disabling HTTPS-Only mode in your browser. In Firefox it's done like this: Hopefully that fixes your issue. |
It'd be nice if it were that simple, but I expect to have a large group of individuals playing with this (20 or so). I'm not sure how the Thanks again! |
What happened?
Working on deploying a proof of concept. Experiencing an issue when attempting to assign a username, post sign up. Turns out that the UI is attempting to communicate via
ws://local.revolt.chat/ws
. Confirmed via the/api
endpoint that none of the configured values are being returned.Expected behavior is for the application to continue into the typical application operation.
The text was updated successfully, but these errors were encountered: