Error - "Data App is not accessible from the web"

[adeimv]

Hello, The connector and communication with our docker worked perfectly before we did the upgrade. Now we are not able to communicate anymore. Has anyone else reported any issues to you? Were there any new ports introduced that now have to be opened? Has anything changed in the connector settings URLs? We also get prompted that some containers are "unhealthy". I am adding some of our error messages into this issue so you can see. Thank you in advance.

Additional: The Docker is on a Linux server for us.

[cchara63]

Hello we have some issues too. We want to know if Data App and ECC URL ports have been changed. Also for ecc URL we were referring to /data/ folder and ports 8889. While now we can still provide something we can't consume getting always an internal server error 500. Moreover while we have upgraded the docker files and even created a new folder while on the other PCs tests are passed it seems that inside the server docker we get the error Local API version is old where the server is running but we get OK communication for the clients.

[gtouloupos]

We receive the same error "Data App is not accessible from the web" on a Centos7 machine. We were using http to access the machine exposed ports locally and but we also used the method of a reverse proxy (HA proxy server) that was communicating with the machine inside our network by exposings https ends and then do http connection inside. both configurations were working before at least in terms of communication. Right now we receive Data App is not accessible from the web too.

[HeliasEurodyn]

Hello. All the ports are remaining the same, so you shouldnt have any issue with ports. Please check once more the Upgrade guide https://github.com/european-dynamics-rnd/OneNet/wiki/OneNet-Upgrade-Guide-to-the-Latest-Version

Also consider checking the below aspects:

Firstly after loggin in on the Ui remember to clear the browser's cache by CTRL + SHIFT + R just to make sure that you received all the latest updates on your browsers.

Next please look on the Connector Check section on your dashboard and let us know about the message that you receive.

if you receive a message indicating that

1. Local Application Not Found probably the local application is not running on your pc or the Local Api Url url is wrong on the Connector Settings menu on the Onenet Ui. You must check the Url (The http://localhost:30001/api is correct) OR restart the Local Application.

You can also download the latest version of the the Local Application from the Useful documents menu

2. Local API Application Version is Old you probably missed the part of installing the new version of the Local Application on the client pc that you work on. You can download it from the Useful documents

3. Data App cannot be found probably the docker installations are not running on the server OR the Data App url is wrong on the Connector Settings so the server is inaccessible.

4. Data App cannot be accessed from the Web means that everythig is installed properly, but the Data App & Ecc url cannot be accessed on the web so you should contact your network administrator to expose those 2 on the internet. Also please consider that after exposing them you must provide the public urls to the onenet from the Connector Settings. As we checked right now most of the users did not finish with this step yet.

5. Connection is established then everything should work fine.

You must be at least on the 4. Data App cannot be accessed from the Web step to be able to provide data on the onenet. Please provide us feedback about your current status on those and after we can procced and solve the other issues that you mention.

[barkalinowski]

Hello, I have had 'Data App cannot be accessed form the Web' too, but after some reinstalling and restarting my PC I do not get this issue anymore. But now I have other issue and I see that you mentioned this issue in your answer @HeliasEurodyn - now I have 'Local API Application Version is Old' error. I have updated and reinstalled all components - from docker to local application downloaded from 'Useful documents' and this error appears not allowing me to fully use app. Not sure what more I can do.

[HeliasEurodyn]

Hello barkalinowski. On the pc where you run the application try to open this url on your browser http://localhost:30001/api/onenet.html

You should see this

The Onenet Local Application must be the v1.3. If you dont see this try downloading from 'Useful documents' and reruning the application.

Please also consider that this Onenet Local Application is per client pc so consider doing this for all the pcs that you work on. Also remember to start the Onenet Local Application when you restart your pc because it doesnt start automatically. If you want to automatically start this on every time that you restart your pc please let me know and I will send you the steps for this.

If it doesnt work for any reason please mail me at helias.karagozidis@eurodyn.com and state your availability there to schedule a call and set it up together.

[adeimv]

Dear @HeliasEurodyn, thank you for your reply, we have no problems with the LocalApp, the connection is fine, but the Data App is still not accessible from the web. I have refreshed my browser multiple times and tested the ports 8889 and 8084 communication, and it works fine (over telnet and normal ping). Do you think reinstalling the docker completely would make thinks work? We have a Linux server for the docker, the Local App is running on our Windows PCs.

[HeliasEurodyn]

It is a network issue, I suggest to contact to your network administrator to regulate this.

You can check this by the below steps:

I see on the system that your registered Data App url is <your Ip>:8084 So if you open a browser from anywhere on the internet (Outside your Vpn) and type <your Ip>:8084/about/version you should be seeing this screen, which does not happen.

So it is clear that you need to expose it on the ineternet and you will finally get the Connection is established message. Thank you.

[gtouloupos]

Dear Elias, We have gone throught your reply however we want to be more spesific now about the ports and issues we have too. We have updated everything as the documentantion and tryied both windows and linux server, and we can confirm the below:

1. Our data app is accesible throught the internet, inside and outside our network. (through a public network)
2. Connector Check option is working and shows everything is up
3. In our configuration we have exposed the 2 ports through reverse proxy using HA proxy load balancer to archieve https communication. We can send the configuration part if needed of the front proxy server. We have not exposed the broker since as we understood this does not needed. So we use direct communication to internal ip for that. is that true? or does 1026 needs to be exposed too? We you are using a reverse proxy from an exposed server to the actual host machine which is reachable from local network for the 2 ports that need to be exposed.
4. We can normally upload-provide a file for example:
5. But we can never consume that file getting a server error 500 after a while. We are wondering if the problem is on reverse proxy configuration. What is that that may prevent us from consuming a file and is this completely impemented or did we missed something on the procudure of uploading a file and consuming it?

[HeliasEurodyn]

gtouloupos please try once more to Refresh the Application on the browser by CTRL + SHIFT + R & consume the file and let us know if it works.

[cchara63]

Dear HeliasEurodyn,

Regarding what you asked @gtouloupos to do, we did the Refresh of Application and the problem is still the same. We are doing all the steps for upload and download a document as we did with the previous application version (which occasionally has worked), but the issue of the new version is still the same (as @gtouloupos has already reported).

Thank you, Charalambos UCY

[adeimv]

Dear @HeliasEurodyn, we have tried the ":8084" step and it works (outside of vpn). We have also tried reinstalling the docker one more time, but it still does not work for us. We are not able to connect. The local API works fine. Do you have any meeting option? To organize a call and check where the mistake is with our IT team? Thank you in advance, Amila (EIMV)

[adeimv]

Dear @HeliasEurodyn and other, today I tried to access my connector settings and I got the message "forbidden".