v5.1.3 Android Client

[cserzs]

Hi Alex,

I used the netxms-server-5.2.4-x64.exe file for the upgrade, as my system has less than 250 nodes.
Another experience is that the netxms-webui-5.2.4-x64.exe cannot be downloaded from the https://netxms.com/downloads page.

Best regard, Zsolt

[Filipp Sudanov]

Yes, looks that there's still a bug with webapi packaging, will check with developers. 
Webui should now be available for download (but, just in case, you can use any 5.2 webui or desktop ui with 5.2.4)

[cserzs]

Hi Filipp,

Thank you in advance. Is there a chance that the problem will be fixed in the next version?

BR, Zsolt

[alk]

It's fixed in upcoming 5.2.5

[cserzs]

Hi Alex,

I upgraded to version 5.2.5. Then, when I added the line "Module=webapi" to the \\NetXMS\etc\netxmsd.conf file, the core NetXMS service
started without any problem (it always stopped with the previous version).
Despite this, unfortunately, the mobile app still does not connect to the server (error code: 404).
I access the server from my mobile phone via a VPN connection.
What is the syntax of the "Hostname or IP" parameter in the mobile app?

BR, Zsolt

[Filipp Sudanov]

The syntax is URL-like
http://hostname:port or http://IP:port

It's adviced to put e.g. nginx as reverse proxy to add ssl (then url would obviously by https://), but if you use VPN you are good with just http

[alk]

@cserzs said in v5.1.3 Android Client:

What is the syntax of the "Hostname or IP" parameter in the mobile app?

You can check if endpoint is correct - it should return information about the API itself, something like:

{"description": "NetXMS web service API", "version": "5.2.3.21", "build": "5.2-366-g15daea330f", "apiVersion": 1}⏎

[cserzs]

Hi,

Thank you for your support.
Can this webapi test be performed in a browser, e.g. with the URL "http://ipaddress:port/webapi"?
I tried this, but unfortunately I didn't get any results.

If I enter the Hostname or IP parameter in the format http://ipaddress:port in the Android app, I get an error code 500.

[WSallade]

Have exact same issue. v5.2.6 on Debian, getting error 500 with Android app. 

Have webapi module loaded and get http://<server ip>:8000 returns "{"description": "NetXMS web service API", "version": "5.2.6", "build": "5.2-443-ge9a696f0c2", "apiVersion": 1}", so this looks good.

[Filipp Sudanov]

Can you capture network traffic on server's 8000 port using tcpdump (tcpdump -s 0 -w snmp.pcap port 8000) or Wireshark if you are on Windows.
You can send resulting file to me via private message.

Also check netxmsd log, may be there are some error messages there.

[tolimanjo]

I was getting the '500' error from the client when using HTTP, and a packet capture showed HTTPS style connection attempts to the server. Perhaps Android was trying to be helpful?
Anyway, putting an HTTPS-HTTP proxy in front of the server (and specifying https:// on the client) fixed the problem.

[alk]

@tolimanjo said in v5.1.3 Android Client:

I was getting the '500' error from the client when using HTTP, and a packet capture showed HTTPS style connection attempts to the server. Perhaps Android was trying to be helpful?
Anyway, putting an HTTPS-HTTP proxy in front of the server (and specifying https:// on the client) fixed the problem.

if protocol is not specified in the connection string, https:// is added.

[cwl]

@tolimanjo said in v5.1.3 Android Client:

Anyway, putting an HTTPS-HTTP proxy in front of the server (and specifying https:// on the client) fixed the problem.

Indeed, with nginx and a few lines in config it works via https.

As for now it doen't look like offering much - no information on nodes, dashboard not working; will be implemented one day, I hope.
Thq question is: the application does not notify about alarms as I can see. Is that correct?

[NosekTomas]

Hi,
I'm starting to play around with NetXMS and I can't seem to connect the new application. Or rather, I can't get the WebAPI to work/open.

I used NetXMS a long time ago, and now I'm coming back to it. Back then, there was still the old Android application, which communicated via its mgmt port.

Unfortunately, I couldn't find any documentation on how to get this new application up and running; the documentation refers to the old version.

If I understand this thread correctly, the application requires the new WebAPI – the one that is set up as a module in netxmsd.conf (not the old one that was installed via a war file and tomcat).

I added the following section to netxmsd.conf:

Module = webapi

[WEBAPI]
ListenerPort = 8000

According to the logs, it looks like the module has loaded, but is it only accessible from the localhost address?  I haven't been able to change this in any way. Port 8000 is not available when trying to connect to the netxms server.

root@netxms-testing:/etc# ss -tulpn | grep 8000
tcp   LISTEN 0      4096       127.0.0.1:8000       0.0.0.0:*    users:(("netxmsd",pid=8114,fd=21))

Can anyone please help me or send me a link to existing documentation?

Thank you very much.

[Filipp Sudanov]

@nosektomas said in v5.1.3 Android Client:

Hi,
I'm starting to play around with NetXMS and I can't seem to connect the new application. Or rather, I can't get the WebAPI to work/open.

I used NetXMS a long time ago, and now I'm coming back to it. Back then, there was still the old Android application, which communicated via its mgmt port.

Unfortunately, I couldn't find any documentation on how to get this new application up and running; the documentation refers to the old version.

If I understand this thread correctly, the application requires the new WebAPI – the one that is set up as a module in netxmsd.conf (not the old one that was installed via a war file and tomcat).

Hi and welcome back

Mobile app expects the endpoint to be https, while server module produces only http. Prior to 6.0.2 recommendation was to put nginx in reverse proxy mode. In 6.0.2 now includes reproxy, which is started by server process. You need to generate certificate files and then the following server config should work:

[WEBAPI]
TLSEnable = yes
TLSCertificate = /opt/netxms/etc/server.crt
TLSCertificateKey = /opt/netxms/etc/server.key
TLSPort = 8443

Documentation is a bit behind because this is work in progress, but should be updated soon.

[NosekTomas]

Thank you very much for your reply.

Yesterday, I found out that when I add the following to the configuration:

[WEBAPI]
Address = 0.0.0.0
Port = 8000

the HTTP API becomes accessible from 0.0.0.0 – i.e. from outside of the system. I also found out that the application requires HTTPS when examining it with Wireshark. So I set up a reverse proxy ngnix in front of it and the app connected.

Thank you very much for the [WEBAPI] TLS configuration. I will try to add it so that I don't need an external proxy.

Is there a list of configuration options for [WEBAPI] somewhere? I tried about 10 options for writing "Address = 0.0.0.0". And I didn't find the TLS option (thanks for that).

But then - I found that when I open a node in the APP, I get an error:

Error: java.lang.NumberFormatException: For
input string: "action"

Is this normal?

Thank you very much!

Best regards,
Tomáš Nosek

[alk]

it's known issue, I'll publish app update soon

[NosekTomas]

@filipp-sudanov said in v5.1.3 Android Client:

Hi and welcome back

Mobile app expects the endpoint to be https, while server module produces only http. Prior to 6.0.2 recommendation was to put nginx in reverse proxy mode. In 6.0.2 now includes reproxy, which is started by server process. You need to generate certificate files and then the following server config should work:

Code Select Expand

[WEBAPI]
TLSEnable = yes
TLSCertificate = /opt/netxms/etc/server.crt
TLSCertificateKey = /opt/netxms/etc/server.key
TLSPort = 8443

Documentation is a bit behind because this is work in progress, but should be updated soon.

Thanks a lot. I tried to configure the built-in reproxy according to the instructions, but it won't start. And I dont know why 

[Filipp Sudanov]

Reproxy on linux needs it to be installed manually, as it's not easily available from package. On linux we might use something else in the future. So currently nginx is the way.

Supported parameters are basically Address and Port, Address supports "*" or "any" to bind to all interfaces. (https://github.com/netxms/netxms/blob/master/src/server/core/webapi.cpp#L410)

Rest of params are for reproxy which is not relevant if using nginx (https://github.com/netxms/netxms/blob/master/src/server/core/webapi_tls.cpp#L205)

[Filipp Sudanov]

UPD: reproxy has no repository, but there's .deb package - you can just install that: https://github.com/umputun/reproxy/releases