Latest Contributions by AlexisRodriguez

Hi Tarig, First of all, I think you have made a mistake in the code. After putting your proxy you have forgotten to add a comma (",") at the end of the line (in both types of requests - lines 36 and 45), therefore a SyntaxError message is shown in command window. Besides, I don't know how you have your network configured but maybe you should have to write your whole http proxy server URL. For instance, in our case, we had to write it with the protocol and port as well: proxy: 'http://proxy.our.company.com:port' Regards! ... View more

Hi Tarig, hi Zhifang,Workaround given in Working with WebAppBuilder behind a corporative http proxy‌ worked for us! So, Tarig, check if it could be as helpful for you as it was in our case. Best regards! ... View more

Hi Junshan, Everything went right with that modification. Thank you very much! ... View more

Hi Zhifang, AFAIK, due to the fact that we are not the network administrators, we are behind a http(s) proxy which captures all mentioned traffic to the Internet being itself who finally sends/gets the contents, making first a filter of the contents asked and evaluating if they are convenient for the environment we are in. So, in any application who needs access to the Internet, it is mandatory to configure this proxy to access any content. I.e. configuring it on Internet Explorer (or whichever browser you use) under the label “Connections”à LAN Settings à Proxy Server. With this firewall/proxy deployment, there is no machine except the proxy server who has http(s) access. While the traffic is sent via Chrome, we can access arcgisonline as the proxy is configured in the browser, but, we have sniffed http traffic by application and we noticed that the web app builder sends traffic by itself (the server mounted) so it cannot access the Internet, with the result of not being able to validate our application on arcgisonline. Thanks. Best regards. ... View more

Hi Tarig, As I commented in other post you have made, our team was experiencing exactly the same issue as you. Every screenshot you have posted gives same error messages than ours. Yesterday we found out that the reason why we could not log in properly was the fact that we were working behind a corporative proxy. If you sniff all http requests while using app builder you'll see that portal url checking is made by the browser directly (browser knows we are behind a proxy) and that's why you've got a green check after validated. However, credential validations are made through a javascript class ("proxy.js") where the connection is lost, throw an error of access and shutdowns the nodejs server. We tried same webapp in a machine outside the office and everything worked fine. We were able to log in properly and start using it! We have already reported this bug to Esri Beta Community and I opened another discussion in GeoNet asking for solutions to configure WebAppBuilder so as to work behind a corporative http proxy. Working with WebAppBuilder behind a corporative http proxy‌ Therefore, please, check if you are working in the same scenario than us. Thanks, Alexis ... View more