- How do I start ArcGIS Web AppBuilder (developer edition)?
- What should I do when I try to set the app ID and encounter an Invalid redirect_uri error?
- How do I start Web AppBuilder (developer edition) in HTTPS websites with my CA-signed certificate?
- How do I use the local help?
- What should I do when I fail to log in to my ArcGIS Online organization or my ArcGIS Enterprise portal?
- How can I update the app ID for Web AppBuilder (developer edition)?
- Is SSL-enabled access supported?
- Which portal securities are supported?
- What should I do when I fail to start Web AppBuilder by specifying a URL to a portal with LDAP authentication?
- Are portals with disconnected environments supported?
- Why can't my deployed app access cross-domain resources?
- Do I have to register my downloaded app for deployment?
- Which versions of ArcGIS Enterprise should I use?
- What should I do if I received the error message "failed to create the app"?
- How do I start ArcGIS Web AppBuilder (developer edition) as a service in Linux?
See Get started.
It is indicated that the URI of Web AppBuilder is not added or set correctly in the Redirect URI list when you registered the app ID for Web AppBuilder in your ArcGIS Enterprise portal. Complete the following steps:
- Browse to the /server directory of the Web AppBuilder installation and delete the signininfo.json file.
- Review step 4 and update the existing app ID with the correct redirect URIs. See View and update app registration info. Alternatively, you can create a new app ID from scratch.
- Refresh the browser running Web AppBuilder.
- Provide your app ID again and click Continue.
If your portal only accepts CORS requests from specified domains, add the machine hosting Web AppBuilder (developer edition) to the portal's allowed origins list. Otherwise, after users sign in via the OAuth prompt, Web AppBuilder redirects back to https://:3344/webappbuilder/?action=setportalurl instead of accessing the app on your portal.
Web AppBuilder uses a self-signed certificate in Node.js to support HTTPS. If you want to start Web AppBuilder in your full HTTPS site, you can use your own certificate. To do so, replace two files in the server directory: cakey.pem and cacert.pem. See Node.js and https://www.openssl.org/docs/faq.html#USER3 for more information.
What should I do when I fail to log in to my ArcGIS Online organization or my ArcGIS Enterprise portal?
You may fail to log in to your ArcGIS Online organization or your ArcGIS Enterprise portal due to one of the following:
- No trusted certification available. To work around it, log in to your portal first to make the certificate trusted, and then log in to Web AppBuilder again.
- Need proxy to access externally. To work around it, set the proxy for Web AppBuilder from node command node server.js [-proxy=value].
What should I do when I fail to start Web AppBuilder by specifying a URL to a portal with LDAP authentication?
When you start Web AppBuilder by specifying a URL to a portal with LDAP authentication, you may encounter this error: Unable to access [Portal_URL]. A Server with specified hostname could not be found. This is probably caused by the SSL support in the node server not matching the SSL version of the LDAP server. To work around it, stop the node server, and then start it with command lines.
On 64-bit Windows, type node_x64.exe server.js -sslClientVersion=SSLv3_method.
On 32-bit Windows, type node_x32.exe server.js -sslClientVersion=SSLv3_method.
On other platforms, type node server.js -sslClientVersion=SSLv3_method.
Open a command window and browse to the server directory of the Web AppBuilder installation.
You need to set the appropriate proxy in the app config.json file. Refer to Use proxy.
The app created by Web AppBuilder can be downloaded and hosted on your web server. Any app that is downloaded must be registered with ArcGIS Online or ArcGIS Enterprise if the app references nonpublic items. Refer to Deploy app.
The developer edition of Web AppBuilder is run as a node app in Linux. You can manage Web AppBuilder with PM2. The following are detailed steps:
- Install pm2 using command $ npm install pm2 -g.
- Navigate to the Server folder of Web AppBuilder.
- Run pm2 start server.js.
This will add Web AppBuilderapplication to PM2's process list. PM2 automatically assigns an App name (based on the filename, without the .js extension) and a PM2 id. PM2 also maintains other information, such as the PID of the process, its current status, and memory usage.
- To launch the application, run pm2
startup systemd in the command window.
You must run this command with super user privileges.
After that, PM2 will generate a command.
- Run the newly generated command to set PM2 up to start on boot (use the command from your own output).