All Apps and Add-ons

Splunk add-on builder doesnt't work with IPv6 and behind reverse proxy

MaverickT
Communicator

Since I can't submit a case I would like to inform you that Splunk add-on builder doesn't work if my instance listens on IPv6 and is behind a reverse proxy (I am not sure if the later thing has any effect). I am running the latest version of Splunk Enterprise and Add-on builder.

The internal log shows the follwing error:

2020-04-22 12:27:20,061 ERROR   [5ea01c08067fd58014dc50] error:335 - Traceback (most recent call last):
  File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cprequest.py", line 628, in respond
    self._do_respond(path_info)
  File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cprequest.py", line 687, in _do_respond
    response.body = self.handler()
  File "/opt/splunk/lib/python3.7/site-packages/cherrypy/lib/encoding.py", line 219, in __call__
    self.body = self.oldhandler(*args, **kwargs)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/htmlinjectiontoolfactory.py", line 75, in wrapper
    resp = handler(*args, **kwargs)
  File "/opt/splunk/lib/python3.7/site-packages/cherrypy/_cpdispatch.py", line 54, in __call__
    return self.callable(*self.args, **self.kwargs)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/routes.py", line 383, in default
    return route.target(self, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3662>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 40, in rundecs
    return fn(*a, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3660>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 118, in check
    return fn(self, *a, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3659>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 166, in validate_ip
    return fn(self, *a, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3658>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 245, in preform_sso_check
    return fn(self, *a, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3657>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 284, in check_login
    return fn(self, *a, **kw)
  File "</opt/splunk/lib/python3.7/site-packages/decorator.py:decorator-gen-3656>", line 2, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 304, in handle_exceptions
    return fn(self, *a, **kw)
  File "/opt/splunk/etc/apps/splunk_app_addon-builder/bin/aob/aob_common/metric_collector/metric_util.py", line 81, in func_wrappers
    ret = func(*args, **kwargs)
  File "<string>", line 43, in is_user_allow_to_user_tabuilder
  File "/opt/splunk/etc/apps/splunk_app_addon-builder/bin/aob/aob_common/metric_collector/metric_util.py", line 81, in func_wrappers
    ret = func(*args, **kwargs)
  File "/opt/splunk/etc/apps/splunk_app_addon-builder/bin/tabuilder_utility/common_util.py", line 250, in create_splunk_service
    'pool_maxsize': 5})
  File "/opt/splunk/etc/apps/splunk_app_addon-builder/bin/splunk_app_add_on_builder/solnlib/net_utils.py", line 129, in wrapper
    'Illegal argument: {}={}'.format(arg, value))
ValueError: Illegal argument: host=::1
0 Karma
1 Solution

MaverickT
Communicator

I had solved the problem by disabling listenOnIPv6 in this instance's server.conf since this particular instance can "survive" only running on IPv4.

server.conf

[general]
listenOnIPv6 = no

View solution in original post

0 Karma

MaverickT
Communicator

I had solved the problem by disabling listenOnIPv6 in this instance's server.conf since this particular instance can "survive" only running on IPv4.

server.conf

[general]
listenOnIPv6 = no
0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...