Skip to content
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

Unknown error: Load failed when logging in or signing up from a reverse proxy #25

Closed
buresdv opened this issue Aug 2, 2024 · 3 comments

Comments

@buresdv
Copy link

buresdv commented Aug 2, 2024

I just spun up Huly and put the frontend behind reverse proxy. I forwarded myIP:8087 (default for the frontend) to dash.mydomain.org. This domain, along with all of its subdomains, have a properly-configured and functioning SSL.

Now, when I try to log in or create a new account through the domain, I get the error Unknown error: Load failed. This does not happen if I access Huly directly through myIP:8087.

Snímek obrazovky 2024-08-02 v 21 50 12

No errors are logged into any of the containers, but the console does show this error:
Fetch API cannot load http://myIP:3000/ due to access control checks.

I have not changed anything in the Compose file, apart from changing the port of minio to 9003 due to another service already running on that port.

Can this be solved in a manner that would maintain security, and without having to expose the account service?

@aonnikov
Copy link
Member

aonnikov commented Sep 2, 2024

I believe the problem is that you exposed only the front service. Huly requires not only front, but several more services to be accessible - transactor, account, collaborator.

@buresdv
Copy link
Author

buresdv commented Sep 3, 2024

Doesn't that sound like a huge security issue? Is it really necessary to expose anything but the frontend?

@aonnikov
Copy link
Member

That probably does, but now we have an example of configuration that exposes only the frontend. You can check it out here: https://github.com/hcengineering/huly-selfhost/tree/main/nginx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants