Different OS incompatibility or flask crash when too many peers (Original Problem: Unable to see / add peers inside a configuration: TypeError: '<' not supported between instances of 'int' and 'str')

Describe The Problem Installed the dashboard service on top of an existing wireguard server with multiple peers. I’m unable to see anything inside of the configuration. The log file shows a traceback: TypeError: ‘<’ not supported between instances of ‘int’ and ‘str’

Expected Error / Traceback

Please provide the error traceback here

[22/Jun/2021 20:20:37] “GET /get_config/wg0 HTTP/1.1” 500 - [2021-06-22 20:20:59,820] ERROR in app: Exception on /get_config/wg0 [GET] Traceback (most recent call last): File “/usr/local/lib/python3.6/site-packages/flask/app.py”, line 2447, in wsgi_app response = self.full_dispatch_request() File “/usr/local/lib/python3.6/site-packages/flask/app.py”, line 1952, in full_dispatch_request rv = self.handle_user_exception(e) File “/usr/local/lib/python3.6/site-packages/flask/app.py”, line 1821, in handle_user_exception reraise(exc_type, exc_value, tb) File “/usr/local/lib/python3.6/site-packages/flask/_compat.py”, line 39, in reraise raise value File “/usr/local/lib/python3.6/site-packages/flask/app.py”, line 1950, in full_dispatch_request rv = self.dispatch_request() File “/usr/local/lib/python3.6/site-packages/flask/app.py”, line 1936, in dispatch_request return self.view_functionsrule.endpoint File “dashboard.py”, line 406, in get_conf “peer_data”: get_peers(config_name), File “dashboard.py”, line 186, in get_peers result = sorted(result, key=lambda d: d[‘status’]) TypeError: ‘<’ not supported between instances of ‘int’ and ‘str’

To Reproduce Please provide how you run the dashboard

Home page shows Wg0. When selecting Wg0 returns blank page with navigation on left still visible. Can activate / deactivate the interface.

OS Information:

• OS: CentOS Linux release 8.3.2011
• Python Version: 3.6.8

Sample of your .conf file

[Interface]
Address = 10.200.200.1/24
SaveConfig = true
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens32 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens32 -j MASQUERADE
ListenPort = <Listen port>
PrivateKey = <Private Key here>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = 10.200.200.3/32
Endpoint = <Client Generated>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = 10.200.200.4/32
Endpoint = <Client Generated>

[Peer]
PublicKey = <Public Key here>
AllowedIPs = 10.200.200.6/32
Endpoint = <Client Generated>


Please provide a sample of your configuration file that you are having problem with. You can replace your public key and private key to ABCD...

[Account] username = ABCD password = ABCD

[Server] wg_conf_path = /etc/wireguard app_ip = 0.0.0.0 app_port = 10086 auth_req = true version = v2.0

[donaldzou]

Bug fixed on the newest release 😉 Running 80+ peers now should be fine, please file another bug report if it is still causing bug in the newest version 😃

[donaldzou]

Hi! Thank you for replying back, I’m gonna re-open this bug report since is gonna remind me to fix it lol. I’m gonna test on multiple OS and also simulate more peers running and figure out what is going on 😉