Unable to connect to proxy facing public endpoint for ION API (Non infor suite)

Hi all,

I am trying to configure a client's REST endpoint into ION API. It uses the basic authentication. I have configured this in the ION API forms.

But now when I try to create a connection point for the same, and when try to select one of the endpoints. Upon clicking the "Select" buttonI am getting the following error.(Please refer the image).

It seems that I am not able to access the port 7443 for my server. Can anyone please guide me with the entire process of ION API registration and thereby selecting one of them in the connection point. What roles are needed for the same. Also how does one access the proxy API for non-infor suites.

Thank you in advance!!

Find more posts tagged with

ION API Gateway

Accepted answers

All comments

Legacy Contributor

This occurs as soon as you press the Select button?

If so, this error may be caused by the Document Flow engine not being able to connect to the API Gateway's Metadata APIs. The Metadata APIs tell clients like Document Flow what APIs are available. Please open a Support Incident to further troubleshoot the problem.

Legacy Contributor

Hi Keith,

Thank you so much for such an early response.

Yes this occurs when I click the 'Select' Button. I have raised the corresponding incident as suggested by you. Let's see what happens

Legacy Contributor

I think this is more of a routing/firewall issue and you need to forward the ports to 7443 as you are getting a http 500x response.

The HyperText Transfer Protocol (HTTP) 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

This error response is a generic "catch-all" response. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future.

You can also ask your server admin or provider to access your error logs and find evidence for the root cause of your problem.

Legacy Contributor

You might also check permissions in the Grid Manager. I troubleshooted a similar issue for a week or so with the help desk because the error was so vague. Turned out to be a disabled permission in the Grid Manager.

Legacy Contributor

Kane do you recall which permission needed to be enabled?

Copyright © 2025 Infor. All rights reserved.