SOLVED Updating Advance Settings via GUI breaks its ability to Connect with the Event Socket

[Sunny Gosain]

SYSTEM VERSION:V4.4.3 Debian 9.9

BUG DESCRIPTION: If I edit the settings (Changed Listen Address to :: or for that matter any field update using the GUI) then the GUI is unable to connect to event_socket. Though fs_cli and all other no GUI functions (like call routing) work fine. I am even able to connect to socket remotely using ESL. The issue prevails even after restarting freeswitch (or rebooting the server).

No ACL change was made.

If the xml file is edited by hand then there is no issue. So somehow the update from the User-Interface breaks the Interface's ability to connect with the Event Socket.
sudo ss -ntlp | grep 8021
LISTEN 0 5 :::8021 :::* users("freeswitch",pid=9028,fd=77))

Confirmed that freeswitch is running as www-data:
ps -aef | grep freeswitch
www-data 3423 1 0 01:58 ? 00:02:45 /usr/bin/freeswitch -ncwait


Confirmed that freeswitch is listening on port 8021


The xml file (after GUI update) is:


File Permission:
ls -alh /etc/freeswitch/autoload_configs/event_socket.conf.xml
-rw-r--r-- 1 www-data www-data 300 Dec 16 07:21 /etc/freeswitch/autoload_configs/event_socket.conf.xml

 

[Adrian Fretwell]

I know you can use :: to represent ::1, the IPv6 loopback, but maybe the GUI is not seeing :: as a valid IP, have you tried putting in ::1 instead?

adrian@a2es-test1:~$ ping -6 ::
PING ::(::) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.030 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.039 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.027 ms

 

[Sunny Gosain]

@Adrian Fretwell Thank you for the tip. I got it working by :
1. creating an ACL record
2. In Advanced-->settings change the Event Socket IP address to 0.0.0.0
3. modifying the XML file (shown below) to incorporate the ACL created in step#1
4. Restart freeswitch: sudo systemctl restart freeswitch

Apparently we need to do both steps#2 and #3 in that sequence. The sequence is relevant because It seems (to me) that if we change the settings via GUI (#2) it will overwrite/default the apply-inbound-acl statement in the XML file





If we

 

[Len]

I am able to run ESL remotely by changing the Event Socket IP Address to 0.0.0.0 or :: and adding the ACL info. The issue is that when I do so, I loose local ESL connectivity, hence fs_cli and GUI features that connect to ESL don't work.
It seems that 0.0.0.0 denies loopback. Is that possible ?