Andrew Mwesigwa Posted December 30, 2014 Share Posted December 30, 2014 Hi, How can I get the error http/1.1 internal Server Error 43531 solved I get it when I'm configuring the Netscaler gateway, Thanks Link to comment Share on other sites More sharing options...
CarlStalhood Posted December 30, 2014 Share Posted December 30, 2014 Is DNS configured on the appliance? Follow http://support.citrix.com/article/CTX139963 to configure Gateway. Link to comment Share on other sites More sharing options...
Andrzej Starmach1709152599 Posted December 30, 2014 Share Posted December 30, 2014 Andrew, there appears to be a problem with connectivity to StoreFront server ...* could be incorrect FQDN of StoreFront (or LB vserver if you do load balance SF servers) - try IP instead for test* check if correct store name ...* could be wrong subnet IP defined -Andrzej Link to comment Share on other sites More sharing options...
Julio Héctor Aguilar Renteria Posted October 1, 2015 Share Posted October 1, 2015 hello, how they have solved this error: Http/1.1 Internal Server Error 43531 Link to comment Share on other sites More sharing options...
Johannes Norz Posted October 4, 2015 Share Posted October 4, 2015 This error appears if NetScaler Gateway (NG) can't connect to StoreFront (SF). If you like outdated technology you may replace SF with WI.There are several reasons for this: you use names and NG can't resolve this name. Check system -> diagnostics and Ping the name you use in your session policy NG can't connect to SF because a firewall is blocking (that's the most popular reason) NG can't connect because you use a protocol not supported by SF (i.e.: you use SSL but don't have a certificate) you use SSL but the host name does not match I hope this helpsFor more information, especially to secure your NetScaler Gateway check my blog at http://blog.norz.at/making-a-netscaler-gateway-on-netscaler-11-a-bit-more-secure/There are many examples about NetScaler and NetScaler gateway in there ;) Link to comment Share on other sites More sharing options...
Craig Avery1709151721 Posted December 11, 2015 Share Posted December 11, 2015 This error appears if NetScaler Gateway (NG) can't connect to StoreFront (SF). If you like outdated technology you may replace SF with WI. There are several reasons for this: you use names and NG can't resolve this name. Check system -> diagnostics and Ping the name you use in your session policy NG can't connect to SF because a firewall is blocking (that's the most popular reason) NG can't connect because you use a protocol not supported by SF (i.e.: you use SSL but don't have a certificate) you use SSL but the host name does not match I hope this helps For more information, especially to secure your NetScaler Gateway check my blog at http://blog.norz.at/making-a-netscaler-gateway-on-netscaler-11-a-bit-more-secure/ There are many examples about NetScaler and NetScaler gateway in there ;) Link to comment Share on other sites More sharing options...
Craig Avery1709151721 Posted December 11, 2015 Share Posted December 11, 2015 HI I am having the same problem I have a Netscaler gateway VPX 11 Environment: external IP - F5 - Netscaler - Web Interface. The netscalers are on different vlans all addresses are pingable. However when I fail over from Primary to secondary I get the Http/1.1 Internal Server Error 43531 error I am stumped Link to comment Share on other sites More sharing options...
Kari Ruissalo Posted May 16, 2017 Share Posted May 16, 2017 Hi, I have seen this a couple of times now as we're migrating our customers from old platforms to new ones. The problem seems to be for some reason in the name resolution and we are able to dodge this by entering the SF LB IP in to the session policies instead of the FQDN. This behavior seems to be quite constant (still on the late versions of 11.1) so that's one possible resolution. Link to comment Share on other sites More sharing options...
CoreLogic Online Posted August 10, 2017 Share Posted August 10, 2017 We were having issues with this on AWS VPX Netscaler, you could ping the FQDN of Storefront and the XDC but the STAs were saying down in the gateway. All config was fine, firewall rules all OK etc. After a number of hours on a call with Citrix Tech, running packet captures etc, they tried using a MIP instead of a SNIP with the NSIP, & this was the issue. We have exactly the same setup in AWS Asia Pacific using a SNIP & it works fine, the new one was v12 & it didnt. Once the SNIP was delete and a MIP added instead, the STA came up, DNS started resolving correctly without using the FQDN etc. Link to comment Share on other sites More sharing options...
Bishal Karki Posted February 25, 2018 Share Posted February 25, 2018 Hi I am quite new to this, I am now facing the same error "Http/1.1 Internal Server Error 43531" . Can someone please help me as well. I can access storefront through azure windows virtual machines but not through internet using netscaler gateway. I am using netscaler vpx azzure byol (1000) (i guess this is netscaler vpx 12 free version). no error log in netscaler authentication log last log is: "... [1250]: (0-36) send_accept: sending accept to kernel for : ......." all policies also are set as mentoned in the link "http://support.citrix.com/article/CTX139963" regards bishal Link to comment Share on other sites More sharing options...
Bartosz Tyrakowski Posted April 3, 2019 Share Posted April 3, 2019 I have seen this issue, when the Gateway is set to “ICA Only” and there is no session policy applied due to a policy filter by AD groups (i. e. in a multi domain environment, where the AD groups are used to apply different session profiles, with different Single Sign-on Domains). Hope this helps anyone. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.