User login/sign-up error - "The change you wanted was rejected."

[cloopadoop]

1. Signed in with default user.
2. Changed user information.
3. Restarted server, found that the service did not restart. Restarted service.
4. Was able to log in with default credentials but not renamed credentials.
5. Attempted to set docker container to restart (still no luck on that front.)
6. Logging in with default credentials or renamed credentials or creating a new user yields this error:
   

[cloopadoop]

It would appear my issue is that my Apache2 setup has a reverse proxy and is rewriting all URL requests to use HTTPS. Authenticity issue? Not sure, a little out of my depth here, but only thing I can figure out to do is to stick with http, which doesn't feel great. Any pointers?

Still can't seem to get the containers to start up automatically when the VPS power cycles, either...

Also, this is very cool. :)

[sam-morin]

@cloopadoop
I am also having this issue. I'm behind an nginx reverse proxy in a docker container. I am on HSTS TLD so plain HTTP is not an option.

Based on your comment (thank you), after adding:
proxy_set_header X-Forwarded-Proto $scheme;
to my server block, everything seems to be functioning as expected now.

I don't use Apache much but try adding:
RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}
RequestHeader set "X-Forwarded-SSL" expr=%{HTTPS}
to your VirtualHost and see if that resolves the issue.

You may need to install and enable the module, mod_headers if that doesn't work.

The first answer, from 'spaceone' and 'Jay Dinse' here is what I am (almost blindly) using as a reference.

[riggraz]

Hi guys, thanks for reaching out!

Unfortunately, I never run Astuto over SSL either, so right now I can't be much of help. However, I plan on releasing a new version of the demo that runs on https pretty soon (probably at the end of next month), so hopefully I'll be able to dig into the problem.

[riggraz]

Hi, just a quick update.

@byjrack has posted an issue with useful knowledge for setting up nginx and TLS, you may want to check it out here: #203 (comment)

[byjrack]

Yeah I feel like I saw that error more than a couple times when I was figuring out a TLS termination model myself. I don't have an HTTPD config for the reverse, but it shouldn't be too far off of the nginx config. My gut says it's likely a callback looping through the client that may require an 80/HTTP redirect handler to work correctly.