After several hours of looking into this, I'm still stuck on getting coturn's web-admin interface to work. Any help would be very appreciated!
I am running coturn version 4.5.1.1-1.1build2 on Ubuntu 20.04, have turned on "web-admin" in the config file and have the "web-admin-ip" set to the server ip so I can test it without an ssh tunnel. I changed the web-admin-port to 8081. I have a DNS entry set up pointing to the server that runs coturn and have an letsencrypt certificate that I am referencing. I have added an admin user via "turnadmin -A".
=== turnserver.conf ===
...
web-admin
web-admin-ip=<turn-server-ip>
web-admin-port=8081
cert=/etc/letsencrypt/live/<server-domain-name>/fullchain.pem
pkey=/etc/letsencrypt/live/<server-domain-name>/privkey.pem
===================
Pinging "turns:<server-domain-name>" on the
trickle-ice website works, although I don't get any relay candidates like I do for "turn:<server-domain-name>", but that seems to be a different issue.
When I open http://<server-domain-name>:8081, I get a page that says "TURN Server, use https connection for the admin session".
However, when I use https://<server-domain-name>:8081, the browser can't establish a connection. In the coturn log file, I get
=== turnserver.log ===
...
0: IO method (auth thread): epoll (with changelist)
0: IO method (auth thread): epoll (with changelist)
0: SQLite DB connection success: /var/lib/turn/turndb
0: IPv4. tcp or tls connected to: <my-home-ip-address>:62381
0: send_socket_to_admin_server: Failed to register callback on web-admin ioa socket
=================
What is happening / what can I try next?