Web AppBuilder: [INFO] server - No portal URL is set, redirect /webapp builder to /webappbuilder?action=setportalurl

Question

Hi all

I am running Web AppBuilder for developers locally

when I start it and I enter http://localhost:3344/webappbuilder or   http://my computer name:3344/webappbuilder

The command window shows the following error message:

Error: connect ETIMEDOUT

at errnoException (net.js:904:11)

at Object.afterConnect [as oncomplete] (net.js:895:19)

[2015-02-19 08:12:36.296] [INFO] server - No portal URL is set, redirect /webapp

builder to /webappbuilder?action=setportalurl

Also when I "Specify the URL to your organization or Portal for ArcGIS"

it shows the following error message:

[2015-02-19 08:38:33.793] [ERROR] proxy - proxy error { [Error: connect ETIMEDOU

T] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }

Error: connect ETIMEDOUT

at errnoException (net.js:904:11)

at Object.afterConnect [as oncomplete] (net.js:895:19)

Anonymous User · Answer

Howdy!

Can you give this info? It'll help diagnose where things are awry:

* Are you trying to connect to your organization's ArcGIS Online page or your organization's Portal for ArcGIS site?* What is the URL you are using as an input when you're setting the portal URL during the WAB Dev setup?
* Have you already added the WAB Dev edition application to your organization's content?
* Have you already set the allowed referrers for that item?

* What version of WAB Dev are you attempting to deploy?

RebeccaStrauch__GISP · Answer

I'm adding this possible resolution in a few threads (and my blog) since I just spent about 3 weeks with tech support trying to figure out the constant redirect back to the page requesting my AGOL URL.  I hadn't fired up WAB for a few months, so not sure if happened at the July or Sept AGOL update (not related to the version of WAB) and most likely was something I did (maybe a new AGOL option I think I needed?).

On the AGOL Security page, I had my ArcGIS Server machine listed in the "Allow Origins" dialog.  Once I deleted the Domain I had listed, all worked again.  Just another thing to check if the other suggestions do not work.  May need it in the future (CORS related) but right now, leaving it blank is what is required for us.

JunshanLiu · Answer

It seems that your node server can't access the portalUrl you set. Do you have to use a proxy to access the portal url?