PostProcessor - no Elasticsearch node available

[Zeal0us]

The postprocessor seems to not like my ES nodes for some reason:

2019/04/04 06:41:02 /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/logs/logging.go:12: logging setup panic: no active connection found: no Elasticsearch node available

goroutine 1 [running]: broadsoft/dashboard/clientutil.GetConfigAndClient(0xc42006e820, 0x0) /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/clientutil/esclient.go:44 +0x2ef main.main() /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/mains/subexp/subscriber.go:9 +0x26 2019/04/04 06:41:02 /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/logs/logging.go:12: logging setup 2019/04/04 06:41:02 /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/mains/processmaindices/process_ma_indices.go:19: start panic: no active connection found: no Elasticsearch node available

goroutine 1 [running]: broadsoft/dashboard/clientutil.GetConfigAndClient(0xc420058a50, 0xc42004bee0) /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/clientutil/esclient.go:44 +0x2ef main.main() /home/brian/Documents/workspaces/goanalyt-test1/build/src/broadsoft/dashboard/mains/processmaindices/process_ma_indices.go:20 +0xed

Looking around, I figured it's probably using this library: https://github.com/olivere/elastic/wiki/Connection-Problems#how-to-figure-out-connection-problems

But http/https is already prepended in whatever code is a part of the postprocessor, it seems, and I verified I could curl my publish address from my server. I have the log receiver, cdr processor, and other running fine on this same server.
I also see the following logs in audit, indicating it seems to be hitting the node fine:

{"@timestamp":"2019-04-04T06:41:02,109", "node.name":"snipped.node.name", "node.id":"88WmhjKxS5431Ij6uQtEyQ", "event.type":"transport", "event.action":"access_granted", "user.name":"bw_postprocessor", "user.realm":"native1", "user.roles":["postprocessor_role"], "origin.type":"rest", "origin.address":"1.2.3.4:59768", "request.id":"C4zxWi2-Sb-wcndF19QDjQ", "action":"cluster:monitor/nodes/info[n]", "request.name":"NodeInfoRequest"} {"@timestamp":"2019-04-04T06:41:02,229", "node.name":"snipped.node.name", "node.id":"88WmhjKxS5431Ij6uQtEyQ", "event.type":"transport", "event.action":"access_granted", "user.name":"bw_postprocessor", "user.realm":"native1", "user.roles":["postprocessor_role"], "origin.type":"rest", "origin.address":"1.2.3.4:59776", "request.id":"NvGsPttYQT2j-ln_KdQCtg", "action":"cluster:monitor/main", "request.name":"MainRequest"} {"@timestamp":"2019-04-04T06:41:02,231", "node.name":"snipped.node.name", "node.id":"88WmhjKxS5431Ij6uQtEyQ", "event.type":"transport", "event.action":"access_granted", "user.name":"bw_postprocessor", "user.realm":"native1", "user.roles":["postprocessor_role"], "origin.type":"rest", "origin.address":"1.2.3.4:59776", "request.id":"PJ7RC0yPS7OPVykie620Uw", "action":"cluster:monitor/nodes/info", "request.name":"NodesInfoRequest"} {"@timestamp":"2019-04-04T06:41:02,232", "node.name":"snipped.node.name", "node.id":"88WmhjKxS5431Ij6uQtEyQ", "event.type":"transport", "event.action":"access_granted", "user.name":"bw_postprocessor", "user.realm":"native1", "user.roles":["postprocessor_role"], "origin.type":"rest", "origin.address":"1.2.3.4:59776", "request.id":"PJ7RC0yPS7OPVykie620Uw", "action":"cluster:monitor/nodes/info[n]", "request.name":"NodeInfoRequest"}

Given it does manage to pull the node info, I'm wondering if it's something immediately after that, or perhaps it has something to do with sniffing not working properly. Without the code I'm kind of stuck on what to do next.