I just signed up today, and I'm consistently getting a 502 Bad Gateway error when attempting either of the following:
- Logging in via https://meta.sr.ht/login
- Updating my profile via https://meta.sr.ht/profile
I'm attempting to log in from a new browser profile; I don't know if I'll lose access if I log out from my original profile.
For the profile update, it seems to actually succeed (as in, the profile text is saved) despite the error.
As per the instructions on the meta.sr.ht tracker, I'm posting here first.
Hi,
On 9/17/23 00:52, Tom Tobin wrote:
> I just signed up today, and I'm consistently getting a 502 Bad Gateway error when attempting either of the following:> > - Logging in via https://meta.sr.ht/login> > - Updating my profile via https://meta.sr.ht/profile> > I'm attempting to log in from a new browser profile; I don't know if I'll lose access if I log out from my original profile.> > For the profile update, it seems to actually succeed (as in, the profile text is saved) despite the error.> > As per the instructions on the meta.sr.ht tracker, I'm posting here first.
Is this still happening? I suppose by "logging in", you mean when
posting the login credentials? What browser are you using?
Sounds pretty strange, but if the issue persists I'm sure we can figure
it out.
Cheers,
Conrad
NOTE: sending this a second time. My mail server failed to deliver the
first on, because your MX record is not returned by 9.9.9.9. It _is_
being returned by 9.9.9.10, which I suppose means either Quad9 considers
your domain malware, or your DNSSEC is not set up right. Just FYI :)
Hi,
On 9/17/23 00:52, Tom Tobin wrote:
> I just signed up today, and I'm consistently getting a 502 Bad Gateway error when attempting either of the following:> > - Logging in via https://meta.sr.ht/login> > - Updating my profile via https://meta.sr.ht/profile> > I'm attempting to log in from a new browser profile; I don't know if I'll lose access if I log out from my original profile.> > For the profile update, it seems to actually succeed (as in, the profile text is saved) despite the error.> > As per the instructions on the meta.sr.ht tracker, I'm posting here first.
Is this still happening? I suppose by "logging in", you mean when
posting the login credentials? What browser are you using?
Sounds pretty strange, but if the issue persists I'm sure we can figure
it out.
Cheers,
Conrad
Not OP, but I'm also getting a Nginx 502 on login (e.g., can't login to
update anything).
Tried from latest Firefox and Chromium on Linux.
I enter my user/pass, go the next screen for 2FA, and then get the 502
after entering it.
-Logan Marchione
Hey all,
On 9/22/23 21:00, Logan Marchione wrote:
> Not OP, but I'm also getting a Nginx 502 on login (e.g., can't login to > update anything).
For context, this issue was caused by an account's "bio" being longer
than we anticipated. The issue should be fixed properly now, which means
you should be able to log in again, or in case of Tom, bring back your
old bio and still log in.
If it doesn't work on first try, please try clearing any existing sr.ht
cookies. If it still doesn't work after that, please reach out again!
Cheers,
Conrad