-
Notifications
You must be signed in to change notification settings - Fork 56
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
Error with Server Address #69
Comments
I think the forcing to 'https' may be a reverse proxy setting. Within nginx proxy manager, I disabled 'force ssl' and then was able to connect to my instance with http://. With this set, I am able to view the other accounts on the instance that are marked as 'visible in registry'. Perhaps I misunderstand the problem, let me know. As to your second point, is the request to be at the login screen for server A, but type in user@B and have it login there? That shouldn't be difficult to support, but I can see that doesn't work at the moment. I will be refactoring the browser client soon, and will include this feature if that is indeed the request. Thanks for your interest in the project! |
|
|
I've noticed my instance is forcing "https://" in front of the server address. I'm not able to login with "https://" in the address, but I can with subdoman.domain.com - But then I can't add any contacts because I can't change the default server in the contact list which has "https://" in the server address.
Can this be fixed please, and maybe add a function for address overrides. It would be nice to enter user@subdomain.domain.com and the server pulls up the profile directly that way, even if it's on another instance.
Thanks so much. Really liking what you've done so far.
The text was updated successfully, but these errors were encountered: