Status: 500 Error When Registering Custom Widget for Portal 10.5.1

[JasonHarshman]

I am getting the following error when I try to register a custom widget to our Portal. I don't believe the error is a result of the widget since it's one of Robert Scheitlin, GISP‌ custom widgets. 

The error:

Unable to load https://<portal.domain>/arcgis/sharing/proxy?https://<widget.domain>/widgets/PopupPanel/manifest.json status: 500

I can access the manifest in the browser if I go directly to https://<widget.domain>/widgets/PopupPanel/manifest.json. So I'm not sure if it's an issue with Portal or the web server hosting the widget that's causing the error.  

[RobertScheitlin__GISP]

Jason,

   What version of the Popup panel are you using in your Portal?

[JasonHarshman]

2.6

[DougLogsdon2]

I came across a similar problem. Your webserver must be CORS enabled (as well as some other settings) to successfully complete the request. Refer to this checklist:

http://enterprise.arcgis.com/en/portal/latest/use/add-custom-widgets.htm

[JasonHarshman]

CORS seems like the probable culprit, but I've gone through that checklist and applied the changes to the webserver and I still get the status 500 error. The widgets are hosted on an Apache webserver. Below are the relevant parts of the httpd.conf I've modified to try and follow that checklist.

LoadModule mime_module modules/mod_mime.so

LoadModule mime_magic_module modules/mod_mime_magic.so

LoadModule headers_module modules/mod_headers.so

#

DocumentRoot "/usr/local/apache2/htdocs"
<Directory "/usr/local/apache2/htdocs">

   Require all granted
   Allow from all
   Satisfy Any
   Header set Access-Control-Allow-Origin "*"

</Directory>

#

<IfModule mime_module>

   TypesConfig conf/mime.types

   AddType application/json .json

</IfModule>

#

MIMEMagicFile conf/magic

[DougLogsdon2]

Two additional errors in my log when I tried setting things up:

1) The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

2) The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'.

[JasonHarshman]

Thanks, Doug. Nothing like that is showing up in the server log, but the portal logs throw this error:

URL 'https://<widget.domain>/widgets/PopupPanel/manifest.json' is not accessible: Error. sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.

[DougLogsdon2]

Jason, I'm not much of a server guy, but it looks like SSL certificates are the culprit at this point in the solution hunt. 

[AleksandraZietara]

Hi Jason,

Have you ever solved this problem? I am experiencing the same behavior of my Portal...

[ClémentLaskar]

Hi,

I also get the same issue, is there any solution ?

Thank you