-
Notifications
You must be signed in to change notification settings - Fork 15
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
How to permit all hosts using ALLOWED_HOSTS #78
Comments
Try |
I did, but unsuccessfully. This is what I found in the log of archyve-archyve-1:
192.168.1.4 is the address of the docker box where archyve is runnin on. |
Interesting... I don't think this issue is caused by ALLOWED_HOSTS. It looks like you were hitting /, getting redirected to /users/sign_in, then getting rejected. The API is under /v1, e.g. /v1/collections to list collections. You'll need to set the API auth headers if you haven't already. Are you writing a client, trying to connect another, existing app, or something else? |
Just try to login into archyve web server from my laptop web browser pointing http://xxx.xxx.xxx.xxx:3300/ |
Ah, I see. I have found a few other people with the same error in other apps, and in all cases they seem to be accessing the app through a reverse proxy, like NGINX. Are you accessing Archyve through NGINX or another reverse proxy? |
Actually not yet. I'directly connect via LAN address |
I'm trying to reproduce, so I ran Archyve in the container on another machine, but I was able to connect without issue. I added the I've just cloned the repo and run I also had docker listen on :80 instead of :3300 so I could just type the URL without port into the address bar in a browser to see if that generated an issue, but everything still worked. Questions:
|
@virdb Did you get it to work? |
I noticed the new variable, but I don't understand how to use it to enable all hosts.
I commented it out , but still no login is possible from outside.
How can I enable all hosts or subnets?
Thanks a lot and best regards
The text was updated successfully, but these errors were encountered: