Manifest URL used in Portal for ArcGIS throws an error
When following the Workflow tutorial, after creating a simple workflow I go to Portal for ArcGIS and select My Content - Add Item - An application - Then I click the button for "Application Extension (App Builder)" & enter the Manifest URL per the instructions:
I get this error: Unable to load https://gis.[OUR COMPANY NAME].com/portal/sharing/proxy?https://apps.geocortex.com/workflow/latest/dist/wab/2.4/widgets/2D/WorkflowRunner_Panel/manifest.json status: 400
Does anyone know why?
-
Hello Tony,
Are you able to load that URL directly in a browser? Looking at the URL that you provided, it looks as though your system's proxy settings are blocking your access to it as I'm able to configure these settings currently.
Thanks, Stefan
0 -
Stefan thanks for the quick reply. When I put that URL directly in the browser it returns the following with no issue: (See attached image)
I'm guessing the proxy issue would be an IT thing then? Correct?
0 -
Hi Tony,
No problem. That would be my guess, perhaps the Portal for ArcGIS Administrator has configured it to act as a proxy server (http://enterprise.arcgis.com/en/portal/latest/administer/windows/restricting-the-portal-s-proxy-capability.htm)?
Stefan
0 -
Sorry this is not the solution.
please provide the solution on how to remove the error in portal.
0 -
Hello - We are seeing the same issue. How did you get this resolved?
Thanks,
Claire
0 -
Hi all,
If you follow the steps outlined in the link I mentioned previously and include 'apps.geocortex.com' in the list of allowedProxyHosts, this may solve the issue. You must also be signed into Portal as an administrator.
I hope this helps.
Thanks, Stefan
0 -
Hi Stefan,
We made that change but still receive an error message: Unable to load https://apps.geocortex.com/workflow/latest/dist/wab/2.4/widgets/2D/WorkflowRunner_Panel/manifest.json status: 0
Any other thoughts?
0 -
Does your organization have a firewall in place that might be blocking outgoing requests?
0 -
I'm running into the same issue. I can access the manifest.json file through the browser, but when trying to create the application in Portal I'm getting the error.
0 -
We have this problem too. Any solution? By default, our portal's proxy capability is unrestricted, but still having issues.
0 -
Hi Ryan and Cody,
A few questions:
- What version of Portal are you seeing this issue with?
- Are you using SaaS or on-prem installations of Designer?
Another option is to deploy the widgets to your web server directly, as outlined in our docs.
Thanks, Stefan
0 -
Hi Stefan-
- Portal 10.7.1
- On-prem
0 -
- Portal 10.7.1
- SaaS
0 -
@Cody Barrett? , so you are using Portal 10.7.1 to host your workflows and widgets. Are you using the public manifest URL? Does the error appear when you are trying to register them in Portal for the application item?
0 -
@Stefan Schweigert? Yes, we are trying to use Portal 10.7.1 to host our widgets and workflows. I'm trying to use the local copy of the manifest url.
Local:
[https]://[host.domain.com]/[virtual_path]/wab/widgets/2D/WorkflowRunner_Panel/manifest.json
0 -
Hi Ryan,
I just retested that I was able to deploy the widgets through SaaS and our testing Portal 10.7.1 and was able to add them using the instructions in our docs. What is the specific error that you are seeing when you try to add the item? Does Chrome DevTools give you any more information?
Thanks, Stefan
0 -
Hi Stefan,
I get the same error in Chrome dev tools and the interface:
Error
Unable to load https://[dns alias]/mobileportal/sharing/proxy?https://apps.geocortex.com/workflow/latest/dist/wab/2.4/widgets/2D/WorkflowRunner_Panel/manifest.json status: 404
Tried in IE just for fun, and same issue.
0 -
I am actually getting a 500 error for our internal facing Portal, and a 404 error for our external facing Portal.
0 -
Does it matter that the widgets from on-prem geocortex uses WAB version 2.4, but portal 10.7.1 uses WAB version 2.12?
0 -
I am seeing a CORS block in the console, that didn't show up in the network traffic. FYI.
dojo.js:141 Access to XMLHttpRequest at 'public: https://apps.geocortex.com/workflow/latest/dist/wab/2.4/widgets/2D/WorkflowRunner_Panel/manifest.json' from origin 'https://[portal]' has been blocked by CORS policy
0 -
Hi Cody,
The 2.4 in the path is an indication that the widgets are supported from 2.4 and newer versions. We retest the widgets against every new release of WAB, so yes, they are supported in 2.12 and 2.13.
Thanks, Stefan
0 -
Hi Ryan,
Since you are using an internal Portal that appears to be more tightly secured, you will likely need to add "https://apps.geocortex.com" to the allow Allow Origins section to permit requests to the SaaS server.
Thanks, Stefan
0 -
@Stefan Schweigert? I'm not sure how, but I was able to create the WorkflowRunner_Panel widget. However, the widget is not showing up in the add widget dialog.
0 -
@Cody Barrett? : Did you share the workflow widgets with any workflow authors in your organization?
0 -
Yes, it's shared with a group, whose members can make workflows.
0 -
Stefan, getting back to this... regarding 'Since you are using an internal Portal that appears to be more tightly secured, you will likely need to add "https://apps.geocortex.com" to the allow Allow Origins section to permit requests to the SaaS server.'
Settings > Security in Portal.... The CORS is set to allow everything by default, so I don't think there is anything specific to allow. Any further thoughts on this?
You'll see in this article it is open by default.
0 -
Another note on this, and just discovered... Looking at my notes. I did have this working on a 10.6.1 Portal a few months ago. Since upgrading to 10.7.1, it is not working. I didn't think that the upgrade could cause the issue, but I am starting to wonder. Can anyone else test this? Does it work in 10.6.1 Portal and not 10.7.1 (upgraded, not fresh)?
0 -
Hi Ryan,
We recently tested GXWF 5.12 widgets against Portal 10.7.1 using both deployment patterns and did not see any issues, so I'm suspecting there might be something specific to your environment.
An upgrade of Portal shouldn't have an impact on widgets as they are simply a reference to the external CDN that hosts the widget data.
With that being said, we've come across numerous issues with Portal upgrades in the past, so we avoid them while doing QA as they introduce too much uncertainty. Could you try to remove the previous widget item in Portal and re-register the widgets and see if they are functional?
Thanks, Stefan
0 -
Hi Stefan,
I deleted the item (application, not widget) in My Content in that Portal. I created a new Application Extension (AppBuilder), with the manifest.json url, and get a 400 error.
0 -
Hi Ryan,
I'll try to reproduce the upgrade scenario and see if we experience the same issue.
Thanks, Stefan
0
Please sign in to leave a comment.
Comments
40 comments