You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently many instances that serve instance pages via a reverse proxy on non-instance domains for various reasons. For example, if an instance's domain name is aaa.com, it could potentially be served at bbb.com or 123.aaa.com. Using Aria in this case will result in incorrect host issues, which can cause a number of anomalies and inconveniences.
The solution is that you should get the real instance domain name from (domain)/api/meta
🥰 Expected Behavior
see above
🤬 Actual Behavior
Users that are supposed to be 123@aaa.com are incorrectly shown as 123@bbb.com or 123@123.aaa.com
📝 Steps to Reproduce
Use the non-instance domain (in this case is bbb.com or 123.aaa.com) and login.
💻 Environment
Not related
Do you want to address this bug yourself?
Yes, I will patch the bug myself and send a pull request
The text was updated successfully, but these errors were encountered:
💡 Summary
There are currently many instances that serve instance pages via a reverse proxy on non-instance domains for various reasons. For example, if an instance's domain name is
aaa.com
, it could potentially be served atbbb.com
or123.aaa.com
. Using Aria in this case will result in incorrect host issues, which can cause a number of anomalies and inconveniences.The solution is that you should get the real instance domain name from
(domain)/api/meta
🥰 Expected Behavior
see above
🤬 Actual Behavior
Users that are supposed to be
123@aaa.com
are incorrectly shown as123@bbb.com
or123@123.aaa.com
📝 Steps to Reproduce
Use the non-instance domain (in this case is
bbb.com
or123.aaa.com
) and login.💻 Environment
Do you want to address this bug yourself?
The text was updated successfully, but these errors were encountered: