Unable to create API proxy in on-prem setup

[nagashree_b]

I am unable to create a new API proxy or import an existing API bundle on the on-prem setup.

I get an error as attached. I checked the system.log and the transactions.log in the message-processor folder. They had no errors listed.

Any clues what could be the issue?

[#2]

It would help if you can provide system logs files.

[anilsr]

Dear @Nagashree B ,

Just FYI, If you see some info / logs you are posting as confidential, Please mask / remove / strike the data before you post the same on public community so that you won't end up sharing confidential information related to your ORG. For Example, From above screenshot i can see your management ui IP, ORG Name, Your Proxy name etc etc.

I have masked the details and updated the screenshot 🙂

Cheers,

Anil Sagar

[nagashree_b]

systemlog.txt renamed it to .txt

[#5]

I need the log file of the managment server. I think you have provided message processor log.

[nagashree_b]

@Anil, thanks

[nagashree_b]

@sriki77 Management server log attached.

[nagashree_b]

Management server log

[#9]

Hmm...i see the error in the logs. can you give me you proxy bundle...with enough data to simulate the issue. Is this happening with every proxy or one specific proxy?

[nagashree_b]

@sriki77 This is happening for every proxy I try to create. I tried with Node.js hello world option available in the wizard and also tried importing the attached proxy. In both cases I get the same error.

[nagashree_b]

Proxy bundle attached

[#12]

This works well on cloud. Seems like an issue with you setup. Please check with the folks who manage your private cloud.

[nagashree_b · Accepted solution]

Yep, I exported the proxy bundle from my apigee cloud account. I reinstalled the on-prem setup and now able to create a new proxy and import the bundle as well.