IIS Proxy - URL Rewrite - Causing Login Issue

[ThePieMonster]

I have Huginn running in a Docker Container and can interact with it just fine by going to host_ip:port.
However, when trying to setup a IIS Proxy so I can have a URL pointed at Huggin (ex: huggin.domain.com) I receive the below when attempting to login.

The change you wanted was rejected.
Maybe you tried to change something you didn't have access to.

Is there something that needs to be configured in Huginn to allow proxy requests? Has anyone setup with IIS URL Rewrite before?

[ThePieMonster]

In my .env file I have the following.

DOMAIN="huginn.domain.com"
PORT="3000"

IIS URL Rewrite is setup the same way I have for other sites also. Only having a issue with Huginn. Any suggestions?

[ThePieMonster]

Solved with the following Server variables

Found this to be helpful.
#2569
https://stackoverflow.com/questions/34680786/iis-equivalent-of-proxy-set-header-x-forwarded-proto-https

[ThePieMonster]

Still having a issue with the services auth however. Unsure if its related or not.

http://huginn.domain.com/auth/twitter

[degan6]

Hey ThePieMonster

Huginn produces a few log files that will be helpful to look at here.

I'd start with the docker logs for the container.

You could also try switching production to debug to try to see the stack trace.

[ThePieMonster]

@degan6

Switched the logging in the config from the 1st line to the 2nd line.

# RAILS_ENV=production
RAILS_ENV=debug 

However in the active .env config I see RAILS_ENV="production" (which is actually listed twice, once at the top of the config file and once towards the bottom of the config file).

Also as shown here, it seems as though the setup_env file is just going to reset this to production anyway...