-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Cannot create form #134
Comments
Hey @j0fr3y, I was unable to reproduce that with my setup. Anything else you did there? Do you use a proxy in front of the app? |
Hey Philipp, unfortunately not. I did double check with this command. |
I have the same error - clean install # Create Docker Volume
docker volume create input-data
# Run the container using port 8080 on the host
docker run -d -p 8080:8080 --name input \
-v input-data:/var/www/html/storage \
ghcr.io/deck9/input:main |
@PhilReinking I ran into the same issue. No proxy, just the vanilla image. Steps to reproduceDeployed with docker-compose (Docker Standalone 20.10.20)
Container starts succesfully and the registration process can be done. However, after the setup is done, GET on
Edit:
Container Log
|
I have the same issue. Same setup as above, but trying with Firefox. |
I was playing around and somehow had the feeling, it's because of an missing tls encrypted connection to get cookie data etc. However I'm still not 100% sure, what is the reason, why a plain |
@f0sh thanks for the docker-compose.yml. I tried to reproduce it like that. For me, it works as long as I access it directly without proxy via localhost:8080. I get the unauthenticated error only if I set up a Proxy in front of the docker image. The reason it then stops working is, that the app uses a stateful authentication via cookies. There is a middleware preventing the cookies from working if the Host is not trusted. Usually, this means setting the Can any of you guys confirm that you had somehow set up a proxy and not set the APP_URL? I mean, if this is the problem, I really need to clarify that in the docs or think of another authentication method that does not produce errors like this. |
As seen in the logs I directly accessed the container without any proxy. However I did not set the I just took my configuration and setup as before and added the
Maybe the missing |
According to deck9#134 the environment variable `APP-URL` needs to be set for the container even when not running behind a proxy, to allow the authentication cookie to be set correctly.
@f0sh thx for testing and the PR. I have an idea what could have caused the authentication error. But I am not sure why it was working on my machine nonetheless. The default config for app url was set to I just released a new version v1.8.3 where the default value for the app_url is also set to I really hope that this was the issue. Would be nice if you could test that again. Regarding your PR, I probably will accept it as it is right now, but extend it a bit to have a more comprehensive guide on hosting the application, especially with a Proxy. |
Don't work for me. Version 18.3. Return 403 error from click on invite link. My docker-compose:
|
According to your configuration, the
I was trying the new version, however out of the box it didn't seem to work for me also with |
I use proxy (digitalocean balancer) |
Ok, thanks for the feedback of you guys. I will need to have a bit more time to look into it, hopefully today! |
Ok, I have another set of instructions for you guys. I already updated the README to include that. If you are running the container behind a proxy, please make sure that your proxy is setting the following headers. Here an example for nginx: location / {
proxy_set_header Connection "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_http_version 1.1;
# Pass the request to the address of the docker container
proxy_pass http://127.0.0.1:8080;
} If the headers are not set, the application fails in using the cookie authentication. Can you confirm if this helps? |
@shurco when using digital ocean you might look into Proxy Protocol Setting: https://docs.digitalocean.com/products/networking/load-balancers/how-to/manage/#proxy-protocol |
Hi, still have issue on clean install My yml file with traefik: services: |
Yesss it works flawless on my Server. 🎉 |
@j0fr3y thanks for testing it out so fast 😄 Will wait for other responses before closing it, but hopefully this issue is solved. |
I'm currently away, but I'll try to test it, mid of next week. |
@f0sh still facing this problem on traefik setup. Later on i will check it with nginx again. |
According to #134 the environment variable `APP-URL` needs to be set for the container even when not running behind a proxy, to allow the authentication cookie to be set correctly.
Setup went great and everythig is installed correctly via docker simple setup, but when i try to create a new form the spinner spins for a second and nothing happens. I am using Safari on an ipad. When opening console. It gives me an 403 Unauthenticated. Settings and API Token generation works.
The text was updated successfully, but these errors were encountered: