Central client for remote server

[lycheeEng]

In the docs, it said that serverlist use zeroconf protocol, so is Central client for local network only?

I have multiple remote servers, I just want to show a brief information about these servers. These servers ip address like 1.1.1.1 and 2.2.2.2, and I want add it into the configure file like this:

[serverlist]
server_1_name=server1
server_1_ip=1.1.1.1
server_1_port=61209
server_1_username=glances
server_1_password=glances
server_2_name=server2
server_2_ip=2.2.2.2
server_2_port=61210
server_2_username=glances
server_2_password=glances

Then I can run glances -w --browser in my computer to see all servers status in one web page.

[RazCrimson]

@lycheeEng
Please use discussions unless there are actual issue/bugs to be reported

In the docs, it said that serverlist use zeroconf protocol, so is Central client for local network only?

Central client would work with all server devices that can be reached (through the network) from your client device.
But zeroconf should be working only for your LAN network.

By the way, you seems to have used different keys than those specified in the docs.
The config should look like:

[serverlist]
server_1_alias=server1
server_1_name=1.1.1.1
server_1_port=61209
server_1_username=glances
server_1_password=glances
server_2_alias=server2
server_2_name=2.2.2.2
server_2_port=61210
server_2_username=glances
server_2_password=glances

[lycheeEng]

@RazCrimson Thank you for your help.

Let me show my circumstances.

My server1 ip is 1.1.1.1 and I connect to glances use domain server1.example.com (cloudflare proxied),
My server2 ip is 2.2.2.2 and I connect to glances use domain server2.example.com (cloudflare proxied), So my configure will be:

[serverlist]
server_1_alias=server1
server_1_name=server1.example.com
server_1_port=443
server_1_username=glances
server_1_password=glances
server_2_alias=server2
server_2_name=server2.example.com
server_2_port=443
server_2_username=glances
server_2_password=glances

I run glances in my server use command /home/ubuntu/.local/bin/glances -u glances -w -p 61209 (the port 61209 do not open to external network, so I can not link to server by ip:61209. I use caddy to reverse proxy 127.0.0.1:61209.)

Then I tested it in my computer using /home/my/.local/bin/glances --config ~/.config/glances/glances.conf -w --browser but it may not connect to my servers.

log:

2023-03-17 09:13:08,984 -- INFO -- Start Glances 3.3.1.1
2023-03-17 09:13:08,984 -- INFO -- CPython 3.10.6 (/usr/bin/python3) and psutil 5.9.4 detected
2023-03-17 09:13:09,000 -- INFO -- Read configuration file '/home/my/.config/glances/glances.conf'
2023-03-17 09:13:09,002 -- DEBUG -- Global refresh rate is set to 2.0 seconds
2023-03-17 09:13:09,176 -- DEBUG -- Zeroconf version 0.47.3 detected.
2023-03-17 09:13:09,178 -- INFO -- Start GlancesClientBrowser mode
2023-03-17 09:13:09,178 -- INFO -- Start reading the [serverlist] section in the configuration file
2023-03-17 09:13:09,190 -- DEBUG -- Add server server1.example.com to the static list
2023-03-17 09:13:09,196 -- DEBUG -- Add server server2.example.com to the static list
2023-03-17 09:13:09,217 -- INFO -- 2 server(s) loaded from the configuration file
2023-03-17 09:13:09,217 -- DEBUG -- Static server list: [{'name': 'server1.example.com', 'port': '443', 'alias': 'server1', 'username': 'glances', 'password': '', 'ip': '104.21.79.253', 'key': 'server1.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}, {'name': 'server2.example.com', 'port': '443', 'alias': 'server2', 'username': 'glances', 'password': '', 'ip': '172.67.172.81', 'key': 'server2.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}]
2023-03-17 09:13:09,218 -- WARNING -- No [passwords] section in the configuration file. Cannot load password list.
2023-03-17 09:13:09,218 -- INFO -- Init autodiscover mode (Zeroconf protocol)
2023-03-17 09:13:09,224 -- DEBUG -- Using selector: EpollSelector
2023-03-17 09:13:09,235 -- DEBUG -- Curses interface compatible with 256 colors
2023-03-17 09:13:09,237 -- DEBUG -- Glances started in 0.233668 seconds
2023-03-17 09:13:09,238 -- DEBUG -- Iter through the following server list: [{'name': 'server1.example.com', 'port': '443', 'alias': 'server1', 'username': 'glances', 'password': '', 'ip': '104.21.79.253', 'key': 'server1.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}, {'name': 'server2.example.com', 'port': '443', 'alias': 'server2', 'username': 'glances', 'password': '', 'ip': '172.67.172.81', 'key': 'server2.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}]
2023-03-17 09:13:09,244 -- DEBUG -- Servers list: [{'name': 'server1.example.com', 'port': '443', 'alias': 'server1', 'username': 'glances', 'password': '', 'ip': '104.21.79.253', 'key': 'server1.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}, {'name': 'server2.example.com', 'port': '443', 'alias': 'server2', 'username': 'glances', 'password': '', 'ip': '172.67.172.81', 'key': 'server2.example.com:443', 'status': 'UNKNOWN', 'type': 'STATIC'}]
2023-03-17 09:13:09,246 -- DEBUG -- Cannot grab stats load_min5 from server (KeyError: 'load_min5')
2023-03-17 09:13:09,246 -- DEBUG -- Cannot grab stats cpu_percent from server (KeyError: 'cpu_percent')
2023-03-17 09:13:09,247 -- DEBUG -- Cannot grab stats mem_percent from server (KeyError: 'mem_percent')
2023-03-17 09:13:09,247 -- DEBUG -- Cannot grab stats hr_name from server (KeyError: 'hr_name')
2023-03-17 09:13:09,248 -- DEBUG -- Cannot grab stats load_min5 from server (KeyError: 'load_min5')
2023-03-17 09:13:09,248 -- DEBUG -- Cannot grab stats cpu_percent from server (KeyError: 'cpu_percent')
2023-03-17 09:13:09,248 -- DEBUG -- Cannot grab stats mem_percent from server (KeyError: 'mem_percent')
2023-03-17 09:13:09,249 -- DEBUG -- Cannot grab stats hr_name from server (KeyError: 'hr_name')
2023-03-17 09:13:09,656 -- DEBUG -- Cannot grab stats from http://104.21.79.253:443 (400 Bad Request)
2023-03-17 09:13:09,757 -- DEBUG -- Cannot grab stats from http://172.67.172.81:443 (400 Bad Request)
2023-03-17 09:13:09,860 -- DEBUG -- Key pressed. Code=258
2023-03-17 09:13:09,861 -- DEBUG -- Server 2/2 selected
2023-03-17 09:13:09,862 -- DEBUG -- Cannot grab stats load_min5 from server (KeyError: 'load_min5')
2023-03-17 09:13:09,863 -- DEBUG -- Cannot grab stats cpu_percent from server (KeyError: 'cpu_percent')
2023-03-17 09:13:09,864 -- DEBUG -- Cannot grab stats mem_percent from server (KeyError: 'mem_percent')
2023-03-17 09:13:09,864 -- DEBUG -- Cannot grab stats hr_name from server (KeyError: 'hr_name')
2023-03-17 09:13:09,865 -- DEBUG -- Cannot grab stats load_min5 from server (KeyError: 'load_min5')
2023-03-17 09:13:09,865 -- DEBUG -- Cannot grab stats cpu_percent from server (KeyError: 'cpu_percent')
2023-03-17 09:13:09,866 -- DEBUG -- Cannot grab stats mem_percent from server (KeyError: 'mem_percent')
2023-03-17 09:13:09,866 -- DEBUG -- Cannot grab stats hr_name from server (KeyError: 'hr_name')
2023-03-17 09:13:09,970 -- DEBUG -- Key pressed. Code=258

[RazCrimson]

@lycheeEng

What are the versions of both the client and the server?
Are they the same?

Also I assume you have Caddy setup properly to passthrough the tcp connection transparently?

[lycheeEng]

Yes, both the version are the same Glances v3.3.1.1 with PsUtil v5.9.4

I am not familiar with Caddy, the caddy configure file just one line:

server1.example.com {
        reverse_proxy 127.0.0.1:61209
}

But now I write a telegram bot to call https://server1.example.com/api, and this bot can send all servers status to me. So if you are not sure what problem is, please close this discussion. Thank you for your help.

[RazCrimson]

@lycheeEng
I think I know what the issue here is.

But now I write a telegram bot to call https://server1.example.com/api, and this bot can send all servers status to me. So if you are not sure what problem is, please close this discussion. Thank you for your help.

If you are using the Web API mode, then Glances Client Browser mode is currently incompatible with that.
Glances web server with multiple client is not implemented. Tracked here: #1770 and #2020

Glances Web API/UI mode (-w flag) exposes an HTTP Server.
Glances Server mode (-s flag) exposes a XML-RPC server, not a HTTP server.
Glances Client Browser mode ( --browser ) uses the exposed XML-RPC server to retrieve stats.

Caddy is a HTTP reverse proxy, so it expects HTTP connections rather than XML-RPC connections.

So if you want the XML-RPC client to work you need to make caddy expose the underlying TCP socket for glances rather than it acting as a reverse proxy.

I am not sure how to do that. Something that might help you with that, in case you are interested: https://caddyserver.com/docs/modules/layer4

P.S. I'll close the discussion since you have another working solution.