Can not upload data on creation of Data entity - Code 500 internal server issue

[cchara63]

Hello,

I am trying to upload a document with Onenet Local application. I selected the "Provide data" below "Data Exchanges" and the "+New" button to create new Data entity. On the field "File" I have upload documents (.csv or .txt or .xlsx), but when I try to save this Entity an error message is presented "Code 500 internal server issue".

Why does this happened? Why I can not upload documents in this Data Entity?

Thank you for your time, Charalambos Charalambous (University of Cyprus - KIOS)

[HeliasEurodyn]

Hello, it is not an issue of Uploading the file. The issue is on the installation of the docker containers & Onenet Local Application.

Please check

1. if you installed properly the Onenet Local Application by Clicking the "Check Connection" button on the "Connector Settings".
2. if you properly deployed the docker containers
3. If you properly configured the adresses of "Data App", "Ecc Url", "Broker Url" on the "Connector Settings".

Please let us know if it worked.

[vsakas]

Charalambos, if this issue has been resolved, please close it. Otherwise please revert to us again.

Best regards,

Vassilis

[cchara63]

Dear Vassili,

regarding your instructions:

Please check

1. if you installed properly the Onenet Local Application by Clicking the "Check Connection" button on the "Connector Settings". -> the "Check Connection" is success!
2. if you properly deployed the docker containers -> I did this on Windows 11 server, with our IT help 3.If you properly configured the adresses of "Data App", "Ecc Url", "Broker Url" on the "Connector Settings". -> I use the "localhost" for the server PC, and the "Servers local IP" for other PCs in same network.

The issues with the upload has solved, but now I can not do new "My Subscription" from the one to the other user. No any error code appears, the application just not respond.

thank you for your time! Charalambos

[HeliasEurodyn]

Hello @cchara63.

1. Regarding "Data App" & "Ecc Url", those ust Be Publicly Exposed In A Static Ip Via Https To Be Served As An Endpoint For Peer To Peer File Transfer. By the Onenet Architecture, the required files to be transferd from/to your premisses to other consumers/providers are encrypted and shared peer to peer, through those Ips/Ports, that's why this is not an option to leave them on localhost.

2. Regarding "My Subscription" form, it was a temporary minor issue that was appeared yesterday after deploying a new release. It works now.

[cchara63]

Dear @HeliasEurodyn,

1. I will confirm that "Data App" & "Ecc Url" are be Public Exposed in Static Ip ASAP!
2. "My Subscription" and "Provide Data/ Consume Data" are operating now.

Thank you for your help! Charalambos

[cchara63]

Hi Helia,

I had a talk with IT department and they said to me, the way they expose port in public is through Reverse Proxies or using webservers like HA proxy. So they asking me if this docker supports this kind of communication. For example the can give us public URL (eg: https://kiosexample.ucy.ac.cy/test ) which will point to ---> internalPcdockerhostip:8084, https://kiosexample.ucy.ac.cy/data --> aninternalPcdockerip:8889.

Thank you, Charalambos

[ferdinandobosco]

Dear Charalambos, since the communication is over internet I don’t see any issue on using a reverse proxy with naming instead of ip and port. Please proceed in this way and come back to us for any kind of issue.

Ferdinando