Emergency server help: get in touch

FreePBX Asterisk HTTP Bind Address (Mini-HTTP): Check It and Keep 8088 Private (Tested)

Where FreePBX 17 sets the Asterisk mini-HTTP bind address, how to check what it really listens on, and the http_custom.conf override that keeps port 8088 open.

Published Updated 3 min read

Short answer: On FreePBX 17 the FreePBX Asterisk HTTP bind address of the built-in web server (mini-HTTP) comes from the Advanced Settings HTTPBINDADDRESS and HTTPTLSBINDADDRESS, which were 127.0.0.1 on our install. Check what it really listens on with asterisk -rx "http show status" and ss -ltnp, not only the GUI: a [general](+) section in /etc/asterisk/http_custom.conf overrode the GUI value on our server and opened port 8088 to the internet. (Reviewed October 2026.)

The mini-HTTP server carries the Asterisk REST and WebSocket interfaces and, if enabled, Prometheus metrics. It should only be reachable from the PBX itself unless you deliberately serve WebRTC phones from outside. We changed the bind address on our FreePBX 17 lab, tested it from another server on the internet and put it back.

The settings

Advanced Setting (fwconsole name)Value on our labGoes to
HTTPENABLEDtrueenabled=yes
HTTPBINDADDRESS127.0.0.1bindaddr in http_additional.conf
HTTPBINDPORT8088bindport
HTTPTLSENABLEtruetlsenable
HTTPTLSBINDADDRESS / HTTPTLSBINDPORT127.0.0.1 / 8089tlsbindaddr=127.0.0.1:8089

FreePBX writes these to /etc/asterisk/http_additional.conf (the options are described in the Asterisk mini-HTTP server documentation); http.conf only includes that file and then http_custom.conf.

Check the FreePBX Asterisk HTTP bind address

fwconsole setting HTTPBINDADDRESS
asterisk -rx "http show status"
ss -ltnp | grep -E ':(8088|8089) '
grep -n bindaddr /etc/asterisk/http_additional.conf
cat /etc/asterisk/http_custom.conf

On our lab http show status printed Server Enabled and Bound to 127.0.0.1:8088 and the HTTPS server on 127.0.0.1:8089, with the URIs /metrics (Prometheus), /media and /ws. From outside, also try curl -s -o /dev/null -w "%{http_code}\n" http://PBX-IP:8088/: no connection is what you want.

What happened when we opened it

  • fwconsole setting HTTPBINDADDRESS 0.0.0.0 followed by fwconsole reload changed bindaddr to 0.0.0.0, and Asterisk listened on 0.0.0.0:8088.
  • A request from another server on the internet to port 8088 got an answer from Asterisk (404 for an unknown path; 503 for /metrics, because the Prometheus module was loaded but its HTTP endpoint was not enabled).
  • Setting it back to 127.0.0.1 and reloading closed the port again: the outside request got no connection.

When the GUI says 127.0.0.1 but the port is open

Look at http_custom.conf. We tested both ways of overriding the address there:

Content of http_custom.confResult after module reload http
[general](+) + bindaddr=0.0.0.0Bound to 0.0.0.0:8088, whatever the GUI setting says
[general] + bindaddr=0.0.0.0Ignored: still 127.0.0.1:8088

The (+) form appends to FreePBX’s section and wins. A later fwconsole reload left http_custom.conf untouched and the port still open on 0.0.0.0 (we did not test a module upgrade), so an old edit there keeps the port open until someone removes it. Remove the lines, then asterisk -rx "module reload http" and check again.

If you need it reachable

  • WebRTC softphones and some integrations connect to the TLS port (8089). Expose only that one, only to the networks that need it, with a valid certificate; see Asterisk WebRTC setup.
  • Never expose 8088 (plain HTTP) to the internet: it carries the same interfaces without encryption.
  • Put a firewall allow-list in front either way; see FreePBX firewall and intrusion detection.

How we tested

  • FreePBX 17.0.33.2, Asterisk 22.11.0, Debian 12, 20–21 October 2026; outside checks with curl from a separate server.
  • Changed HTTPBINDADDRESS with fwconsole, then tested both http_custom.conf variants; everything was put back to 127.0.0.1 and an empty http_custom.conf afterwards.
  • Not tested: whether a specific module upgrade changes the setting (we could not reproduce such a change), and FreePBX 16.

FAQ

What is the Asterisk mini-HTTP server?

Asterisk’s built-in web server. FreePBX uses it for ARI, WebSockets (WebRTC) and, if enabled, Prometheus metrics. It listens on 8088 (HTTP) and 8089 (HTTPS).

Should port 8088 be open to the internet?

No. Keep HTTPBINDADDRESS at 127.0.0.1 unless something on another machine really needs it, and then prefer 8089 behind an allow-list.

Why is 8088 open although Advanced Settings say 127.0.0.1?

Check /etc/asterisk/http_custom.conf. A [general](+) section with its own bindaddr overrides the FreePBX value.

At a glance

FreePBX Asterisk HTTP (Mini-HTTP) Bind Address: Check It and Keep 8088 Private (Tested) summary card: On FreePBX 17 the FreePBX Asterisk HTTP bind address of the built-in web server (mini-HTTP) comes from the Advanced Settings HTTPBINDADDRESS and HT…
In short: On FreePBX 17 the FreePBX Asterisk HTTP bind address of the built-in web server (mini-HTTP) comes from the Advanced Settings HTTPBINDADDRESS and HTTPTLSBINDADDRESS, which were 127.0.0.1 on our install. Check what it r…

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.