How to configure SSL in V4.40.4 using a proxy

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
2 anni tempo fa
After update NopCommerce from V4.40.3 to V4.40.4 the SSL configuration does not work anymore. TOO_MANY_REDIRECTS is back again.
Before update there was a property "UseHttpXForwardedProto" in appsettings.json, which was set to true. Also the store url was set to https and use ssl to true. All worked fine before update.
Now the structure of appsettings.json has changed (which imo should be in a major update not in a patch update. no offence, just a hint for future updates.) and I have no idea how to set those new properties.
NopCommerce runs behind NginX proxy manager.
Maybe someone can help.


Here is my current appsettings (region "HostingConfig"):

...
"HostConfig": {
    "UseProxy": false,
    "ForwardedProtoHeaderName": "",
    "ForwardedForHeaderName": "",
    "KnownProxies": ""
},
...
2 anni tempo fa
zombieghost wrote:

Before update there was a property "UseHttpXForwardedProto" in appsettings.json, which was set to true.
Now the structure of appsettings.json has changed (which imo should be in a major update not in a patch update. no offence, just a hint for future updates.) and I have no idea how to set those new properties.

Here is my current appsettings (region "HostingConfig"):

...
"HostConfig": {
    "UseProxy": false,
    "ForwardedProtoHeaderName": "",
    "ForwardedForHeaderName": "",
    "KnownProxies": ""
},
...


It's still there. Your version of the HostingConfig is from the develop branch and it'll be only changed in the 4.50 release (see details here).
2 anni tempo fa
Thank you for quick reply. I run NopCommerce in docker. To update I've pulled
https://hub.docker.com/layers/nopcommerceteam/nopcommerce/4.40.4/images/sha256-d91d20d5b49acb98754272e63b7713625388c5f26948b82938154a817a42c6fe?context=explore
and restored the database.

So was that image built from the develop branch?
2 anni tempo fa
zombieghost wrote:
Thank you for quick reply. I run NopCommerce in docker. To update I've pulled
https://hub.docker.com/layers/nopcommerceteam/nopcommerce/4.40.4/images/sha256-d91d20d5b49acb98754272e63b7713625388c5f26948b82938154a817a42c6fe?context=explore
and restored the database.

So was that image built from the develop branch?


Well, I got it. We'll check it. Thanks for the info.
Follow this issue.
2 anni tempo fa
Thank you
2 anni tempo fa
Hi, zombieghost.

We check the nopCommerce 4.40 image on DockerHub and found that it was built on the wrong brunch, now we fixed this problem, try to use a new image.

zombieghost wrote:
Thank you for quick reply. I run NopCommerce in docker. To update I've pulled
https://hub.docker.com/layers/nopcommerceteam/nopcommerce/4.40.4/images/sha256-d91d20d5b49acb98754272e63b7713625388c5f26948b82938154a817a42c6fe?context=explore
and restored the database.

So was that image built from the develop branch?
2 anni tempo fa
Hello Sergei,
thank you. I‘ll try it.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.