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
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.
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?
The text was updated successfully, but these errors were encountered:
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.
I just spun up Huly and put the frontend behind reverse proxy. I forwarded
myIP:8087
(default for the frontend) todash.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 throughmyIP:8087
.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
to9003
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?
The text was updated successfully, but these errors were encountered: