NetXMS Support Forum

English Support => General Support => Topic started by: cserzs on February 20, 2025, 09:30:19 PM

Title: v5.1.3 Android Client
Post by: cserzs on February 20, 2025, 09:30:19 PM
Hi,

Is there Android client for the v5.1.3 release?
If not yet, will it be later?

Thank you in advance and best regards,
Zsolt
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on February 21, 2025, 12:38:07 PM
Hi,

Android client is being reworked - new API was added as server module and Android app is in development. We plan to release it when NetXMS 5.2 is out. If you want to test it before that, you can PM me your Google ID and we will add you to the group of test users.
Title: Re: v5.1.3 Android Client
Post by: cserzs on April 13, 2025, 11:57:51 AM
Hi,

Thank you very much for the previous feedback. Any information on when the ANDROID client will be available again? I cannot find the apk installer in the v5.2 and v5.2.1 files.

Thank you in advance and best regards, Zsolt
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on May 07, 2025, 04:39:41 PM
I'll try to push it into public beta (in the play store) next week
Title: Re: v5.1.3 Android Client
Post by: cserzs on June 06, 2025, 08:11:32 AM
Hi Alex,

Thank you very much for your feedback, but unfortunately I can't find the app in the play store.

BR, Zsolt
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on June 26, 2025, 03:42:08 PM
App has been published:
https://play.google.com/store/apps/details?id=org.netxms.android&hl=en
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 08, 2025, 09:30:12 PM
Hi Filipp,

Thank you for information. I have downloaded and installed the mobile client from google play.
I have successfully updated the server and WEBUI to the latest version 5.2.3.
I connect my phone to the server via VPN (I use the WireGuard app). From the phone I can ping the IP address of the server and access the NetXMS WEB UI from a browser. However, I cannot access the server from the mobile app, I always get an Error: 404 message. In the Hostname or IP text box, I type the IP address of the server (which responds to a ping) and the corresponding username and password, but the mobile app won't connect to the server. What could be the problem?

Thank you in advance and best regards,
Zsolt
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on July 09, 2025, 12:09:19 AM
New Android client uses new WEB API that is a server module. 

Quick setup guide:
- add "Module=webapi,Y" to netxmsd.conf, module listens on port 8000 by default. You can change it:
[WEBAPI]
ListenerPort=12345

Please note, it's unencrypted HTTP!
- add nginx, reproxy, traefic - or any other ssl offloading app in front of it.
- connect to the APi endpoint.

But for testing you can skip this and just use HTTP
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 09, 2025, 09:23:36 PM
Thank you Filipp,

If I add the "Module=webapi,Y" line to the \\NetXMS\etc\netxmsd.conf file, the NetXMS core service always stops and cannot be run.

best regards, Zsolt
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on July 09, 2025, 10:06:20 PM
what's in the logs? Also ",Y" is not required anymore, it's default now.
Which version of the server you are using?
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 09, 2025, 10:28:20 PM
Hi Alex, I use the latest 5.2.3 version. I will check the logs ASAP. 
Best regards, Zsolt
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 10, 2025, 09:44:46 PM
Hi Alex,

The following information about the failed NetXMS core startup is in the netxmsd.log:

2025.07.09 19:56:22.642 *I* [logger            ] Log file opened (rotation policy 2, max size 16777216)
2025.07.09 19:56:22.642 *I* [startup            ] Starting NetXMS server version 5.2.3 build tag 5.2-345-g0ca84eba5b
2025.07.09 19:56:22.642 *I* [startup            ] System time zone is KXX+02KXX
2025.07.09 19:56:22.642 *I* [logger            ] Debug level set to 0
2025.07.09 19:56:22.642 *I* [config            ] Main configuration file: C:\NetXMS\etc\netxmsd.conf
2025.07.09 19:56:22.642 *I* [config            ] Configuration tree:
2025.07.09 19:56:22.642 *I* [config            ] config
2025.07.09 19:56:22.642 *I* [config            ]  +- server
2025.07.09 19:56:22.642 *I* [config            ]      +- DBDriver
2025.07.09 19:56:22.642 *I* [config            ]      |    value: pgsql.ddr
2025.07.09 19:56:22.642 *I* [config            ]      +- DBServer
2025.07.09 19:56:22.642 *I* [config            ]      |    value: localhost
2025.07.09 19:56:22.642 *I* [config            ]      +- DBName
2025.07.09 19:56:22.642 *I* [config            ]      |    value: netxms_db
2025.07.09 19:56:22.642 *I* [config            ]      +- DBLogin
2025.07.09 19:56:22.642 *I* [config            ]      |    value: netxms
2025.07.09 19:56:22.642 *I* [config            ]      +- DBPassword
2025.07.09 19:56:22.642 *I* [config            ]      |    value: ********
2025.07.09 19:56:22.642 *I* [config            ]      +- LogFile
2025.07.09 19:56:22.642 *I* [config            ]      |    value: C:\NetXMS\log\netxmsd.log
2025.07.09 19:56:22.642 *I* [config            ]      +- Module
2025.07.09 19:56:22.642 *I* [config            ]      |    value: webapi,Y
2025.07.09 19:56:22.642 *I* [config            ]      +- ListenerPort
2025.07.09 19:56:22.642 *I* [config            ]          value: 8000
2025.07.09 19:56:22.644 *I* [startup            ] System hardware ID 29BD12835A0F6AC5ECC19D4AF52693A9320DC403
2025.07.09 19:56:22.650 *I* [db.drv            ] Database driver "pgsql.ddr" loaded and initialized successfully
2025.07.09 19:56:22.651 *I* [comm.listener      ] SocketListener/LocalAdmin: listening on 127.0.0.1:21784
2025.07.09 19:56:22.651 *I* [comm.listener      ] SocketListener/LocalAdmin: listening on [127.0.0.1]:21784
2025.07.09 19:56:23.308 *I* [startup            ] Server ID 33C6C28F00000029
2025.07.09 19:56:23.331 *I* [db.writer          ] DBWriter/Housekeeper interlock is OFF
2025.07.09 19:56:23.334 *I* [crypto            ] Crypto library initialized (OpenSSL 3.0.15 3 Sep 2024)
2025.07.09 19:56:23.334 *I* [crypto.cert        ] Server certificate not set
2025.07.09 19:56:23.334 *I* [crypto.cert        ] Internal CA certificate not set
2025.07.09 19:56:23.423 *I* [macdb              ] OUI-24 database loaded (32548 entries)
2025.07.09 19:56:23.430 *I* [macdb              ] OUI-28 database loaded (4403 entries)
2025.07.09 19:56:23.437 *I* [macdb              ] OUI-36 database loaded (5046 entries)
2025.07.09 19:56:23.443 *E* [modules            ] Unable to load module "webapi" (The specified module cannot be found.)

Without the ",Y" the result is the same.

best regards, Zsolt
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on July 11, 2025, 09:48:05 AM
Looks like webapi module was not packaged in 5.1. I recommend you to upgrade to latest (5.2.4 at the moment) version.
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 11, 2025, 10:40:55 PM
I upgraded my server from v5.2.3 to v5.2.4, but unfortunately the situation has not changed.
If I add the line "Module = webapi" to the netxmsd.conf file, the NetXMS core service will no longer start.
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on July 11, 2025, 11:03:47 PM
Do you install from packages or build from source?
Title: Re: v5.1.3 Android Client
Post by: cserzs on July 12, 2025, 10:17:10 AM
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
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on July 17, 2025, 01:45:00 PM
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)
Title: Re: v5.1.3 Android Client
Post by: cserzs on August 12, 2025, 04:12:39 PM
Hi Filipp,

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

BR, Zsolt
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on August 17, 2025, 09:08:58 PM
It's fixed in upcoming 5.2.5
Title: Re: v5.1.3 Android Client
Post by: cserzs on September 24, 2025, 10:40:58 PM
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
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on September 24, 2025, 11:44:13 PM
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
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on September 25, 2025, 01:42:14 AM
Quote from: cserzs on September 24, 2025, 10:40:58 PMWhat 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}⏎                                                                         
Title: Re: v5.1.3 Android Client
Post by: cserzs on September 26, 2025, 10:20:23 PM
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.

Title: Re: v5.1.3 Android Client
Post by: WSallade on September 29, 2025, 06:01:04 PM
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.
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on September 29, 2025, 11:08:31 PM
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.
Title: Re: v5.1.3 Android Client
Post by: tolimanjo on September 30, 2025, 05:41:40 AM
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.
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on September 30, 2025, 10:38:21 PM
Quote from: tolimanjo on September 30, 2025, 05:41:40 AMI 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.
Title: Re: v5.1.3 Android Client
Post by: cwl on December 01, 2025, 06:12:12 AM
Quote from: tolimanjo on September 30, 2025, 05:41:40 AMAnyway, 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?
Title: Re: v5.1.3 Android Client
Post by: NosekTomas on February 17, 2026, 08:11:36 PM
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.
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on February 17, 2026, 11:07:34 PM
Quote from: NosekTomas on February 17, 2026, 08:11:36 PMHi,
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.
Title: Re: v5.1.3 Android Client
Post by: NosekTomas on February 18, 2026, 11:23:36 AM
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"

(https://i.ibb.co/dwWPQdfg/Screenshot-20260218-101836-Net-XMS.jpg)

Is this normal?

Thank you very much!

Best regards,
Tomáš Nosek
Title: Re: v5.1.3 Android Client
Post by: Alex Kirhenshtein on February 18, 2026, 12:34:07 PM
it's known issue, I'll publish app update soon
Title: Re: v5.1.3 Android Client
Post by: NosekTomas on February 18, 2026, 05:25:30 PM
Quote from: Filipp Sudanov on February 17, 2026, 11:07:34 PMHi 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  :-\

(https://i.ibb.co/kVG78jmd/Sn-mek-obrazovky-2026-02-18-162136.png)
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on February 19, 2026, 12:14:05 PM
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)
Title: Re: v5.1.3 Android Client
Post by: Filipp Sudanov on February 19, 2026, 12:30:23 PM
UPD: reproxy has no repository, but there's .deb package - you can just install that: https://github.com/umputun/reproxy/releases
Title: Re: v5.1.3 Android Client
Post by: nichky on February 23, 2026, 11:18:28 AM
when we login from android, i tried
 ip-address:8000
ip-address:4701
ip-address.
No of them are working im getting error 500 and 525